From: stt@houdini.camb.inmet.com (Tucker Taft)
Subject: Re: Language lawyer question - private packages.
Date: 1997/01/21
Date: 1997-01-21T00:00:00+00:00 [thread overview]
Message-ID: <E4D5E6.MsK.0.-s@inmet.camb.inmet.com> (raw)
In-Reply-To: 32E493CA.5001@ozemail.com.au
Chris Miller (chrismil@ozemail.com.au) wrote:
: One for the language lawyers.
: Assume that you have two sets of packages as followes :-
: package A is ... end;
: private package A.B is ... end;
: package A.B.C is ... end;
: AND
: package A is ... end;
: private package A.B is ... end;
: private package A.B.C is ... end;-- * different.
: Once a certain level of the tree is private (A.B), what is the
: significance of making further children (A.B.C) private vs. public ?.
If a child is private, it is only visible to its (immediate) parent, and the
descendants of its parent. Hence, private package A.B.C is visible
to A.B and A.B.*, but not to A. By contrast, a public child
is just as "visible" as its parent. Hence, anything that can see the
parent can see its public children. For example, public package A.B.C *is*
visible to grandparent A, and all descendants thereof (A.*).
: What operations and / or visibility will I have on one set of packages
: that I will not
: have on the other set ?.
: Any takers ?.
See above.
: Chris Miller
: Sydney Australia.
: chrismil@ozemail.com.au
-Tucker Taft stt@inmet.com http://www.inmet.com/~stt/
Intermetrics, Inc. Cambridge, MA USA
prev parent reply other threads:[~1997-01-21 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-21 0:00 Language lawyer question - private packages Chris Miller
1997-01-21 0:00 ` Robert A Duff
1997-01-21 0:00 ` Tucker Taft [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox