Re: Child packages question

["Pat Rogers" <progers@classwide.com>]

"James Ross" <rem.jr@rem.webross.com> wrote in message
news:fug4bukpc28gaqh1sci8m9ql2k1oa54ms5@4ax.com...
> 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...


You should definitely have a look at the Rationale, plus it's free so no need to
go buy another Ada book, although I don't think one can have too many!  :-)