From: Oliver Kellogg <okellogg@users.sourceforge.net>
Subject: Re: "shadow" package hierarchy using renaming of child packages
Date: Mon, 1 Jul 2013 01:29:25 -0700 (PDT)
Date: 2013-07-01T01:29:25-07:00 [thread overview]
Message-ID: <b5c3aebb-1857-4c25-8ec7-fbddec11794a@googlegroups.com> (raw)
In-Reply-To: <22fdedd9-f5e2-4489-bd41-7fb3b21e9992@googlegroups.com>
On Sunday, June 30, 2013 10:43:59 PM UTC+2, AdaMagica wrote:
>
> So was I. But you cannot use a renaming as a parent of a further package.
> So there is no real way to mix two package trees.
Understood. Still, even just one level of child packages would seem interesting. For this to work, IMHO there must be some notion of "structural equivalence" of the shadow root with respect to the original root. In the example, apparently the declaration "subtype T is Foo.T;" in the Shadow package spec creates the structural equivalence.
Meanwhile, I've been able to successfully build the example using an old Apex-3.2.0b.
I'm still not sure of chapter and verse in the RM that defines this.
-- Oliver
next prev parent reply other threads:[~2013-07-01 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 7:00 "shadow" package hierarchy using renaming of child packages Oliver Kellogg
2013-06-30 20:43 ` AdaMagica
2013-07-01 1:34 ` Shark8
2013-07-01 5:46 ` J-P. Rosen
2013-07-01 16:31 ` Adam Beneschan
2013-07-01 8:29 ` Oliver Kellogg [this message]
2013-07-01 9:37 ` AdaMagica
2013-07-01 11:14 ` Oliver Kellogg
2013-07-01 8:21 ` AdaMagica
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox