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.224.169.1 with SMTP id w1mr22800443qay.4.1376245808911; Sun, 11 Aug 2013 11:30:08 -0700 (PDT) X-Received: by 10.49.81.208 with SMTP id c16mr535051qey.34.1376245808881; Sun, 11 Aug 2013 11:30:08 -0700 (PDT) Path: border1.nntp.dca3.giganews.com!border2.nntp.dca3.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!f7no1911647qan.0!news-out.google.com!he10ni1415qab.0!nntp.google.com!fx3no2004466qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sun, 11 Aug 2013 11:30:08 -0700 (PDT) In-Reply-To: <79ec97f1-b5f8-4b12-b351-262fad685f50@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=91.7.21.229; posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf NNTP-Posting-Host: 91.7.21.229 References: <79ec97f1-b5f8-4b12-b351-262fad685f50@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <55ebf370-8f34-406e-b30b-32c0a919be3c@googlegroups.com> Subject: Re: Generics and Child Packages From: AdaMagica Injection-Date: Sun, 11 Aug 2013 18:30:08 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Original-Bytes: 2230 Xref: number.nntp.dca.giganews.com comp.lang.ada:182967 Date: 2013-08-11T11:30:08-07:00 List-Id: On Sunday, August 11, 2013 5:49:06 PM UTC+2, sbelm...@gmail.com wrote: > Though I still don't buy the "children of a generic are a generic" explan= ation. Semantically there is no difference between a nested package and a = child package, so any reason for the latter being "officially" generic (i.e= . requiring instantiation) should also apply to the former, which it clearl= y does not. It's senseless that this should be okay: > generic > package P > private > package C is > ... > end C; > end P; With each instantiation, you get a new C. > but that this should be not: > > generic > package P > ... > end P; > > private package P.C is > ... > end P.C; How should P.C be related to an instantiation of P? P is not a package, onl= y an inst. is a package. Perhaps you could dream up a rule what P.C should = be, but it's not obvious.