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.2.137 with SMTP id 9mr10616961qaj.2.1372671443947; Mon, 01 Jul 2013 02:37:23 -0700 (PDT) X-Received: by 10.49.36.199 with SMTP id s7mr637791qej.17.1372671443928; Mon, 01 Jul 2013 02:37:23 -0700 (PDT) Path: border1.nntp.dca3.giganews.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!j2no3151576qak.0!news-out.google.com!f7ni121qai.0!nntp.google.com!j2no3151570qak.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 1 Jul 2013 02:37:23 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=91.7.22.131; posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf NNTP-Posting-Host: 91.7.22.131 References: <63a787e1-c3d9-4bfd-a7e6-6ff0f0c8236b@googlegroups.com> <22fdedd9-f5e2-4489-bd41-7fb3b21e9992@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <736ca511-696e-47c0-9936-5f6ce0128138@googlegroups.com> Subject: Re: "shadow" package hierarchy using renaming of child packages From: AdaMagica Injection-Date: Mon, 01 Jul 2013 09:37:23 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Original-Bytes: 1978 Xref: number.nntp.dca.giganews.com comp.lang.ada:182171 Date: 2013-07-01T02:37:23-07:00 List-Id: On Monday, July 1, 2013 10:29:25 AM UTC+2, Oliver Kellogg wrote: > Understood. Still, even just one level of child packages would seem inter= esting. For this to work, IMHO there must be some notion of "structural equ= ivalence" of the shadow root with respect to the original root. In the exam= ple, apparently the declaration "subtype T is Foo.T;" in the Shadow package= spec creates the structural equivalence. No, it hasn't anything to do with structural equivalence. Just compare: with P1; with P1; package P2 is package P2.Ren renames P1; package Ren renames P1; end P2;