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: a07f3367d7,5f6b808d2dcff171
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,CP1252
Path: 
 g2news1.google.com!postnews.google.com!s15g2000yqs.googlegroups.com!not-for-mail
From: =?ISO-8859-1?Q?Yannick_Duch=EAne_Hibou57?= <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re: Can a child access private types of its parent?
Date: Sat, 25 Jul 2009 12:57:43 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: 
 <7af39777-c24a-40b7-85e8-d6c9ef9a7297@s15g2000yqs.googlegroups.com>
References: 
 <5607fca0-895c-47ca-abdf-7c9700b20b04@h18g2000yqj.googlegroups.com>
	<e396f69a-3a93-4033-95a4-b199bed653b1@b15g2000yqd.googlegroups.com>
	<a596fd13-d550-42da-b59d-186772c44c41@a26g2000yqn.googlegroups.com>
NNTP-Posting-Host: 77.198.58.193
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1248551863 11143 127.0.0.1 (25 Jul 2009 19:57:43
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 25 Jul 2009 19:57:43 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: s15g2000yqs.googlegroups.com; posting-host=77.198.58.193;
	posting-account=vrfdLAoAAAAauX_3XwyXEwXCWN3A1l8D
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
	fr),gzip(gfe),gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:6384
Date: 2009-07-25T12:57:43-07:00
List-Id: <comp.lang.ada>

Just for the annecdote, the construct in your first layout is named a
=93 nested package =94

And the visibility rules is : the public part of a child package can
only rely on the public part of its parent, while the private part of
the child can access either the public or the private part of the
parent (for specs). This is intuitive and just theere to disallow a
child package to expose what was introduced in a parent as to be kept
private.