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=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d6f7b92fd11ab291 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-07-17 11:14:38 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!tdsnet-transit!newspeer.tds.net!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Crosspost: Help wanted from comp.compilers Date: 17 Jul 2003 13:14:36 -0500 Organization: LJK Software Message-ID: References: NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1058465605 32116 192.135.80.34 (17 Jul 2003 18:13:25 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Thu, 17 Jul 2003 18:13:25 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:40421 Date: 2003-07-17T13:14:36-05:00 List-Id: In article , tmoran@acm.org writes: >> Just looking at files on disk does not give any history as to whether >> a given _declaration_ within a file has changed. One might end up >> recompiling a cascading tree of modules because some entirely unused >> (yet) declaration was added to a module. > If A 'with's B and something new is added to B's spec, how does a > compiler know that the new thing is not used by A, unless it recompiles A? The compilers in question keep in their database an index of everything that A uses. Obviously if A has changed as well it must be recompiled, but that is the trivial case.