From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,37c86f3bf9ffa41c X-Google-Attributes: gid103376,public From: stt@houdini.camb.inmet.com (Tucker Taft) Subject: Re: Language lawyer question - private packages. Date: 1997/01/21 Message-ID: #1/1 X-Deja-AN: 211266695 sender: news@inmet.camb.inmet.com (USENET news) x-nntp-posting-host: houdini.camb.inmet.com references: <32E493CA.5001@ozemail.com.au> organization: Intermetrics, Inc. newsgroups: comp.lang.ada Date: 1997-01-21T00:00:00+00:00 List-Id: 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