From: Oliver Kellogg <okellogg@users.sourceforge.net>
Subject: Re: "shadow" package hierarchy using renaming of child packages
Date: Mon, 1 Jul 2013 04:14:43 -0700 (PDT)
Date: 2013-07-01T04:14:43-07:00 [thread overview]
Message-ID: <7844631e-9668-4471-bc53-9f856e0fb1d7@googlegroups.com> (raw)
In-Reply-To: <736ca511-696e-47c0-9936-5f6ce0128138@googlegroups.com>
On Monday, July 1, 2013 11:37:23, UTC+2 AdaMagica wrote:
>
> > [...] In the example, 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:
> [...]
Yikes, you're right!
Looking from the user perspective:
Imagine Shadow to preexist, with much code written against its API.
Imagine that a new package Foo representing a light-weight subset of the Shadow API is added to the system at a later date. Now the interesting thing is that the existing applications do not need to be changed.
In shadow-test.adb,
I : Shadow.T := Shadow.Child.Create;
the declaration of T in Shadow ensures that.
Thanks.
next prev parent reply other threads:[~2013-07-01 11:14 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
2013-07-01 9:37 ` AdaMagica
2013-07-01 11:14 ` Oliver Kellogg [this message]
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