From: James Ross <rem.jr@rem.webross.com>
Subject: Child packages question
Date: Mon, 08 Apr 2002 19:33:06 -0600
Date: 2002-04-08T19:33:06-06:00 [thread overview]
Message-ID: <fug4bukpc28gaqh1sci8m9ql2k1oa54ms5@4ax.com> (raw)
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
next reply other threads:[~2002-04-09 1:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 1:33 James Ross [this message]
2002-04-09 2:17 ` Child packages question sk
2002-04-09 4:39 ` James Ross
2002-04-09 4:40 ` sk
2002-04-09 6:37 ` Ingo Marks
2002-04-09 3:17 ` Pat Rogers
2002-04-09 3:58 ` Randy Brukardt
2002-04-09 8:28 ` tmoran
2002-04-09 15:11 ` Ted Dennison
2002-04-10 23:02 ` Randy Brukardt
[not found] <3CB24F38.2D03C71A@myob.com>
2002-04-09 2:54 ` Steven Deller
[not found] <000101c1df71$eb7d9920$2137e5c0@rational.com>
2002-04-09 3:22 ` sk
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox