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 X-Received: by 10.36.253.66 with SMTP id m63mr1992607ith.22.1519917586596; Thu, 01 Mar 2018 07:19:46 -0800 (PST) X-Received: by 10.157.22.195 with SMTP id s3mr104248ots.13.1519917586453; Thu, 01 Mar 2018 07:19:46 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!feed.usenet.farm!feeder4.feed.usenet.farm!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!w142no1128348ita.0!news-out.google.com!a2ni3331ite.0!nntp.google.com!w142no1128346ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 1 Mar 2018 07:19:46 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=75.99.9.146; posting-account=s89PEgoAAABHs2ETFyOrCeTQVQJAfzKq NNTP-Posting-Host: 75.99.9.146 References: <55cd79f5-4b37-4b08-b292-073ed2f37021@googlegroups.com> <15c49c4e-726a-4fd7-bf35-c7d27ff9a491@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: body stub not allowed in inner scope From: marciant@earthlink.net Injection-Date: Thu, 01 Mar 2018 15:19:46 +0000 Content-Type: text/plain; charset="UTF-8" Xref: reader02.eternal-september.org comp.lang.ada:50751 Date: 2018-03-01T07:19:46-08:00 List-Id: On Wednesday, February 28, 2018 at 6:23:32 PM UTC-5, Randy Brukardt wrote: > > Does anyone other than ACATS tests actually use stubs these days? Why? (We > used to use them extensively, but only because Janus/Ada on 16-bit MS-DOS > limited a single unit to 64K of generated code -- and our editors couldn't > handle more than 256K of source code at a time. None of that makes sense > today.) Definitely: To teezing out minor differences between big packages due to "the same" program running on updated "hardware": keepping more code "common".