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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,859116256d0a7bc2 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.66.77.3 with SMTP id o3mr736122paw.13.1343469201779; Sat, 28 Jul 2012 02:53:21 -0700 (PDT) Path: p10ni72325294pbh.1!nntp.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: AdaMagica Newsgroups: comp.lang.ada Subject: Re: basic question on nested packages Date: Sat, 28 Jul 2012 02:53:21 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: NNTP-Posting-Host: 91.7.125.76 Mime-Version: 1.0 X-Trace: posting.google.com 1343469201 20606 127.0.0.1 (28 Jul 2012 09:53:21 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Sat, 28 Jul 2012 09:53:21 +0000 (UTC) Cc: nma@12000.org In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=91.7.125.76; posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf User-Agent: G2/1.0 X-Received-Bytes: 1859 Content-Type: text/plain; charset=ISO-8859-1 Date: 2012-07-28T02:53:21-07:00 List-Id: On Saturday, July 28, 2012 11:01:25 AM UTC+2, Nasser M. Abbasi wrote: > The only surprise for me, was that I had to WITH the 'driver' which is a > child package of the parent lapack package explicitly to use it from the > client even though I withed the parent package. > > 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.