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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,53ca16c587912bce X-Google-Attributes: gid103376,public From: nabbasi@earthlink.net Subject: Re: Source files organisation using gnat Date: 1997/07/08 Message-ID: <5pu1ve$dtq@drn.zippo.com>#1/1 X-Deja-AN: 255581525 References: <19970630185901.OAA27670@ladder02.news.aol.com> <5podbt$sn8$1@gonzo.sun3.iaf.nl> Organization: from-home Newsgroups: comp.lang.ada Date: 1997-07-08T00:00:00+00:00 List-Id: In article , dewar@merv.cs.nyu.edu says... > >>Geert said >> >>So what might be useful is to have some kind of compilation server >>that can keep state between compilations and re-use internal datastructures >>like parse trees. Of course in that case you may have to worry about >>memory management and for example restart the server periodically.>> > >Yes, of course, this is an obvious idea, and is exactly what I was >talking about when I said we had some schemes to substantially >speed up compiatlations. In fact we hvae had a detyailed design for >doing this for over a year -- i's on the list! > This does not sound much different in its idea (may be not in implementation) than using a library-based Ada compilation system to store such informations, as is done for example by the VAX/VMS Ada83 compiler, i.e. the traditional Ada compilation system, instead of source-based Ada compilation system such as gnat. no ? Nasser