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=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.6 Path: eternal-september.org!reader02.eternal-september.org!feeder1.feed.usenet.farm!feed.usenet.farm!tr3.eu1.usenetexpress.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Sat, 23 Oct 2021 12:24:18 -0500 From: Dennis Lee Bieber Newsgroups: comp.lang.ada Subject: Re: Ada versus Pascal Date: Sat, 23 Oct 2021 13:24:19 -0400 Organization: IISS Elusive Unicorn Message-ID: <79f8nghgdr1p9707tg924i18t4tmkqdnvr@4ax.com> References: <6pq5ngtioomfo2depk1ickvbdmleuqq16i@4ax.com> <87ilxod1nd.fsf@nightsong.com> User-Agent: ForteAgent/8.00.32.1272 X-No-Archive: yes MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-CdJNApbJlx9zeH9phYZfSlSuL0mikKajap4NehNKjqOmks8TnLXC84h4uTP06/c7KN+lCpI93puSkb/!KsDnpzRfVFHN8mtz5h4AVpROWDIggnqyTR2L0kPti/tYOL2WF63SfZ5QLIqwkqM/OG5U/ecm X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 3223 Xref: reader02.eternal-september.org comp.lang.ada:63066 List-Id: On Fri, 22 Oct 2021 17:29:26 -0700, Paul Rubin declaimed the following: >Dennis Lee Bieber writes: >> Also, Pascal of the era typically did not support separate >> compilation and/or include files -- programs were all single >> monolithic files, any change required recompiling the entire program. > >I thought Ada was originally like that too. The program could be split >into multiple files, but they were expected to all be compiled together. No... Pretty much every build system for Ada focused on only rebuilding the parts affected by a changed file -- by following WITH statements to find required units (see the LRM for what a "unit" comprises) /and/ determining if that unit requires compilation. Timestamps or intermediate files may be used in that determination. Changes in implementation (body) require the body to be recompiled, but if the specification did not change, then units WITHing the specification don't need to be compiled -- they just need relinking with the updated body. GNAT's build system -- using the host OS filesystem as the "database" -- required that separate files are generated for each unit. (cf: GNATCHOP) All-in-One was the optional source file format accepted by some compilers -- but other than the early language reference manuals, I haven't encountered any text books that use that means of presenting code examples (unless it is discussing the use of GNATCHOP itself ). https://www.adahome.com/History/Stoneman/stoneman.htm is the requirements document that DoD used to define the desired environment around Ada development. """ 4.E APSE TOOLSET REQUIREMENTS 4.E.1 The tools in an APSE shall support the development of programs in the Ada language as defined by the Ada reference manual. In particular an APSE shall support the separate compilation features of the language. """ NOTE the last sentence -- Wulfraed Dennis Lee Bieber AF6VN wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/