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=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,859116256d0a7bc2 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII Received: by 10.180.24.202 with SMTP id w10mr331208wif.0.1343789839834; Tue, 31 Jul 2012 19:57:19 -0700 (PDT) Received: by 10.66.89.225 with SMTP id br1mr3229347pab.3.1343789445115; Tue, 31 Jul 2012 19:50:45 -0700 (PDT) Path: q11ni15937998wiw.1!nntp.google.com!12no2311922wil.1!news-out.google.com!p10ni9631000pbh.1!nntp.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nrc-news.nrc.ca!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: "J-P. Rosen" Newsgroups: comp.lang.ada Subject: Re: basic question on nested packages Date: Sat, 28 Jul 2012 14:54:35 +0200 Organization: A noiseless patient Spider Message-ID: References: Mime-Version: 1.0 Injection-Date: Sat, 28 Jul 2012 12:54:33 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="e53b1d06105a4101a995a7820d7abbff"; logging-data="4914"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19rOS7LqXZi81zEKtqKBmAq" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 In-Reply-To: Cancel-Lock: sha1:x2YQwqQy7YMHAO04CxMmaMkSXfI= X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Date: 2012-07-28T14:54:35+02:00 List-Id: Le 28/07/2012 11:53, AdaMagica a �crit : >> I thought, since it is a child package of lapack, then it will be pulled in >> automatically by just WITH'ing lapack. But no. >> i.e. I thought by inviting the parent in, the children will come along >> with the parent and not be left alone outside. > > It's just the other way round. Withing the child implicitly withs the parent: > > with Parent.Child; -- no need to with Parent > > It would indeed be confusing if you could see the child, but not the parent. > It is possible: with Parent.Child; package Parent_Child renames Parent_Child; with Parent_Child; -- brings in only the child Not confusing: you can access the declarations of the child, not those of the parent. This is actually useful if you want to provide a package to users, and you want to make it a child (for implementation reasons), but don't want your users to know that. -- J-P. Rosen Adalog 2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX Tel: +33 1 45 29 21 52, Fax: +33 1 45 29 25 00 http://www.adalog.fr