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:02:11 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!snoopy.risq.qc.ca!nf3.bellglobal.com!wn14feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc04.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Crosspost: Help wanted from comp.compilers References: X-Newsreader: Tom's custom newsreader Message-ID: NNTP-Posting-Host: 12.234.13.56 X-Complaints-To: abuse@comcast.net X-Trace: sccrnsc04 1058464930 12.234.13.56 (Thu, 17 Jul 2003 18:02:10 GMT) NNTP-Posting-Date: Thu, 17 Jul 2003 18:02:10 GMT Organization: Comcast Online Date: Thu, 17 Jul 2003 18:02:10 GMT Xref: archiver1.google.com comp.lang.ada:40418 Date: 2003-07-17T18:02:10+00:00 List-Id: > 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?