From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!gegeweb.org!news.ecp.fr!news.jacob-sparre.dk!loke.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: GNAT GPL is not shareware Date: Mon, 12 Jan 2015 18:00:48 -0600 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: References: <87bnmetex4.fsf@ludovic-brenta.org> <1otenmcbgnvlt$.dn9361nl2jm8$.dlg@40tude.net> <8ryfky4awox2$.q2gfw4pvsgau.dlg@40tude.net> NNTP-Posting-Host: rrsoftware.com X-Trace: loke.gir.dk 1421107248 23503 24.196.82.226 (13 Jan 2015 00:00:48 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Tue, 13 Jan 2015 00:00:48 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-RFC2646: Format=Flowed; Response Xref: news.eternal-september.org comp.lang.ada:24557 Date: 2015-01-12T18:00:48-06:00 List-Id: "G.B." wrote in message news:m90n2n$c2p$1@dont-email.me... ... > Tiny example: > .ali files of GNAT and the ./info files of AdaMagic may > (theoretically) share a schema of Ada library data, > data available on request, leaving hardly any performance hit. That's not really practical; different compilers store very different information in those files. GNAT stores hardly anything in an .ali file, preferring to recompile everything as needed. (A true source-based model.) OTOH, a compiler like Janus/Ada stores pre-compiled data in it's SYM files, it never recompiles anything other than by explicit compile command. The commonality is so small that there isn't much to be gained by a standard for library data. What would happen is that you'd have a definition of "library data" that matched one particular compiler, and either everyone else would have to conform to it (making them less efficient than the one that they had to match) or ignore the "standard" (providing no benefit at all). That's the problem with ASIS, after all. It essentially matches the way that the circa 1990 Rational compiler works (which is downright weird, IMHO), and everyone else either has to bend their technology to match it somehow, or simply not bother and hope the silly thing goes away. I don't see how either does any good unless you really want a single-implementation ecosystem. (Even AdaCore doesn't want that for Ada.) Randy.