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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.107.162.142 with SMTP id l136mr11832839ioe.16.1512339060062; Sun, 03 Dec 2017 14:11:00 -0800 (PST) X-Received: by 10.157.81.193 with SMTP id d1mr564222oth.13.1512339059977; Sun, 03 Dec 2017 14:10:59 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.kjsl.com!usenet.stanford.edu!193no625366itr.0!news-out.google.com!b73ni387ita.0!nntp.google.com!193no625365itr.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sun, 3 Dec 2017 14:10:59 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2601:191:8303:2100:5985:2c17:9409:aa9c; posting-account=fdRd8woAAADTIlxCu9FgvDrUK4wPzvy3 NNTP-Posting-Host: 2601:191:8303:2100:5985:2c17:9409:aa9c References: <889a3aed-4e6b-49c8-8c1c-6f1478e8e077@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <155a33ac-4adf-486b-8a98-42e8794ada82@googlegroups.com> Subject: Re: Full view of a private partial view cannot be a subtype From: Robert Eachus Injection-Date: Sun, 03 Dec 2017 22:11:00 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:49339 Date: 2017-12-03T14:10:59-08:00 List-Id: On Sunday, December 3, 2017 at 1:50:44 PM UTC-5, Simon Wright wrote: =20 > That said, completely forbidding declare blocks is going a step too far! Definitely. I tend to think of the structure of a main program is initializ= ation code, and a declare block for the initializations that have to wait f= or a file to be read. For example, a file with a large matrix preceded by = its dimensions. You can't tell how many tasks you need or where to split t= he file until you see the dimensions. Opening the file in a library packag= e just seems wrong somehow. Also nonce procedures and functions to provide operations on a locally decl= ared type are not really nesting anyway. My rule used to be that if the com= piler was going to inline it, no worries. (Today's compilers are getting a= bit too good at inlining. ;-)