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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d60e0492375aa57a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-07-31 06:22:08 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: Mark.Doherty@uk.thalesgroup.com (Mark Doherty) Newsgroups: comp.lang.ada Subject: Re: Visibility of private packages?? Date: 31 Jul 2002 06:22:07 -0700 Organization: http://groups.google.com/ Message-ID: <2d87db3f.0207310522.7236ea92@posting.google.com> References: NNTP-Posting-Host: 195.173.4.13 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1028121728 20302 127.0.0.1 (31 Jul 2002 13:22:08 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 31 Jul 2002 13:22:08 GMT Xref: archiver1.google.com comp.lang.ada:27521 Date: 2002-07-31T13:22:08+00:00 List-Id: > > Does this mean that if A.B1.C1 is private, it can only be withed by the > bodies of A.B1 and other descendants of A.B1, and specs of private packages > of descendants of A.B1? Yes > > If this is the case, how could I structure things to give the desired > effect? A private child is never visible outside the tree routed at its parent. And within that tree it is not visable to the specifications of public siblings! Try looking in 'programming in ada95 2nd edition' by john barnes page 247. it has a nice diagram. Mark