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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,775bc4aee028e5e9
X-Google-Attributes: gid103376,public
From: falis@ma.aonix.com (Ed Falis)
Subject: Re: Q's: nested packages / visibilty
Date: 1998/11/19
Message-ID: <1104_911490872@DZOG-CHEN>#1/1
X-Deja-AN: 413538330
Sender: news@sd.aonix.com (USENET News Admin @flash)
X-Nntp-Posting-Host: 192.157.137.14
References: <9v6hGdgMLuwN-pn2-VFf4e0fMp6MD@dt182n2f.tampabay.rr.com>
 <matthew_heaney-ya023680001811982323430001@news.ni.net>
Organization: Aonix, San Diego, CA, USA
Newsgroups: comp.lang.ada
Date: 1998-11-19T00:00:00+00:00
List-Id: <comp.lang.ada>

I didn't see the original full post, but it sounds like what Craig is 
after is a private child package:

package Parent is

-- generally visible stuff
private
-- as needed
end Parent.

private package Parent.Restricted is
-- stuff only for use by the parent or other children for 
implementation
private
-- whatever
end Parent.Restricted;

with Parent.Restricted;
package body Parent is
-- implementation
end Parent;

Of course, if he said he was using Ada 83, all bets are off on 
this approach.
- Ed