Re: Generic child units

[Robert A Duff <bobduff@shell01.TheWorld.com>]

Stephen Leake <Stephe.Leake@nasa.gov> writes:

> Robert A Duff <bobduff@shell01.TheWorld.com> writes:
> > Here's the AARM text:
> > 
> >  18    A child of a parent generic package shall be instantiated or renamed
> >  only within the declarative region of the parent generic.
> 
> But in my code above, Chi is an instantiation of "a child of a parent
> generic package", and it is _not_ "within the declarative region of
> the parent generic".

No, Chi is not a child of Parent, it is a child of Par, which is a
package, not a generic package.

> I see. So I actually instantiated Par.Child (as the code actually says
> :), which is _not_ a "child of a generic parent", even though I think
> of it that way. 

That's right.  It's very similar to what happens if you had Child
physically nested within Parent.

The way to think of it is, when you instantiate Parent as Par, you get a copy
of all the children, and they are called (for example) Par.Child.
However you can't *see* them unless you say "with Parent.Child".
The  "with Parent.Child" has a somewhat magical effect: it makes *.Child
visible, for all * that are instances of Parent (Par, in your case).

> That makes sense. As is sometimes the case, the ARM is not immediately
> clear to us non-lawyers.

Well, this is one of the more arcane rules in the language.

- Bob