From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=BAYES_00,XPRIO autolearn=no autolearn_force=no version=3.4.6 Path: eternal-september.org!reader02.eternal-september.org!gandalf.srv.welterde.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: How to challenge a GCC patch? Date: Thu, 30 Sep 2021 19:18:05 -0500 Organization: JSA Research & Innovation Message-ID: References: Injection-Date: Fri, 1 Oct 2021 00:18:07 -0000 (UTC) Injection-Info: franka.jacob-sparre.dk; posting-host="rrsoftware.com:24.196.82.226"; logging-data="25861"; mail-complaints-to="news@jacob-sparre.dk" X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246 Xref: reader02.eternal-september.org comp.lang.ada:62905 List-Id: "J-P. Rosen" wrote in message news:sj3ktk$emb$1@dont-email.me... ... > I'm afraid this is a red herring. I think rather that AdaCore has a hard > time convincing people of moving from the well defined, carefully designed > ASIS to the terrible mess of LibAdalang. The ASIS design and definition is a mess (at least from the perspective of explaining what is expected). We tried to clean it up in the previous ASIS standardization update, but that was a lot of work and we probably didn't match implementations very well. The entire model of ASIS doesn't make much sense for static analysis purposes, it's way too focused on syntax rather than semantics. And it doesn't work well for syntax analysis because it requires a compilable program. So it really has a very narrow use case (if any). Your tool mainly proves that one can use anything with heroic enough efforts. But the effort that your tools goes through to determine basic semantics like whether a type is tagged demonstrates it's hardly a practical way to build a tool. As far as I know, you're the only one that ever managed to do anything beyond proof-of-concepts with ASIS. I can certainly see why AdaCore might not want to support something solely for one usage. I can easily believe that Libadalang is even more poorly defined than ASIS (most vendor-generated things are, regardless of the vendor involved). I would guess that the only way to build a tool like yours is to do your own analysis (certainly, that is how I'd approach it). A true Ada Semantic Interface would be a good thing, but ASIS isn't it. Randy.