Re: Generic child units

[Georg Bauhaus <sb463ba@d2-hrz.uni-duisburg.de>]

Stephen Leake <Stephe.Leake@nasa.gov> wrote:
: Rodrigo Garc?a <rodrigo.garcia.ARROBA.epfl.ch> writes:
: 
:> I need some enlightment in this area... Let us suppose that I have two
:> generic packages declared in separate files and one is the parent of
:> the other:
:> 
:> generic
:>     type Elem is private;
:> package Parent is
:>     type Vector is array (Integer range <>) of Elem;
:> end Parent;
:> 
:> generic
:> package Parent.Child is
:>     subtype Vector2D is Vector (1 .. 2);
:> end Parent.Child;
:> 
:> How can I instantiate the child package 
: 
: with Parent.Child;
: procedure Foo is
:   package Par is new Parent (Elem => Integer);
:   package Chi is new Par.Child;
: begin
: ...
: end Foo;
: 
: Note that the second instantiation is "Par.Child", not "Parent.Child".

I find it useful to compare to this variation of the packages, at least
it has shed some light (I think :-/) as far as the instantiation sequence
is concerned:

generic
   type Elem is private;
package Parent is
   type Vector is array (Integer range <>) of Elem;
   
   generic
   package Child is
      subtype Vector2D is Vector (1 .. 2);
   end Child;

end Parent;

So, elsewhere, you can't have an instance of child without an instance
of parent.

But you can have an instance of Child in Parent's body. I don't
know why, exactely, though.

(No wonder that the editors next door tell me that programmers
are funny people :-)


-- Georg