Re: Child packages question

["Randy Brukardt" <randy@rrsoftware.com>]

Look at private packages (they're really only useful for children). See
10.1.1 in the ARM.

We put all of the bindings in Claw into private packages
(Claw.Low_Level.Windows, Claw.Low_Level.GDI, etc.). Only Claw can with
those packages; users of Claw can't access them.

            Randy.

James Ross wrote in message ...
>I have been holding off on asking because I thought I might figure it
>out myself.  I only have one Ada 95 book (I guess I oughta  buy more)
>and it is not clear on this issue.  As for looking on the net, I have
>browsed, but not extensively.
>
>Is it possible to control accessibility / visibility of packages using
>the child mechanism?
>
>For example; Car and Car.Engine -- I want the user to be able to "use"
>Car but not Car.Engine. The user could call Car.Accelerate_Mph, but
>only the Car package could call Car.Engine.Pump_More_Gas.
>
>Am I all wet here and that is NOT what child packages is all about?
>It appears that Child packages may be just a way of organizing closely
>related functionality and expanding the namespace. Thanks for any
>insights, advice, flames, etc...
>JR
>