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,990196a3d5e5eb5e,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-04-08 18:32:50 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!deine.net!freenix!proxad.net!isdnet!sn-xit-02!sn-post-02!sn-post-01!supernews.com!news.supernews.com!not-for-mail From: James Ross Newsgroups: comp.lang.ada Subject: Child packages question Date: Mon, 08 Apr 2002 19:33:06 -0600 Organization: Posted via Supernews, http://www.supernews.com Message-ID: X-Newsreader: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: newsabuse@supernews.com Xref: archiver1.google.com comp.lang.ada:22248 Date: 2002-04-08T19:33:06-06:00 List-Id: 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