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=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: "Alejandro R. Mosteo" <alejandro@mosteo.com>
Newsgroups: comp.lang.ada
Subject: Re: package organization (is this doable?)
Date: Fri, 29 Jun 2018 20:47:50 +0200
Organization: A noiseless patient Spider
Message-ID: <ph5usm$n62$1@dont-email.me>
References: <ph5k6p$ena$1@dont-email.me> <lya7rdtuto.fsf@pushface.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 29 Jun 2018 18:47:51 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
 posting-host="0599fa98447edc9f248b20a7f2f95401";
	logging-data="23746"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+LLhI0pmcalpxqJ0Goxa7/"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
Cancel-Lock: sha1:JGWxBQ+0NgUDCOH2qkqQnlGfIDE=
In-Reply-To: <lya7rdtuto.fsf@pushface.org>
Content-Language: en-US
Xref: reader02.eternal-september.org comp.lang.ada:53438
Date: 2018-06-29T20:47:50+02:00
List-Id: <comp.lang.ada>

On 29/06/2018 18:34, Simon Wright wrote:
> "Alejandro R. Mosteo" <alejandro@mosteo.com> writes:
> 
>> package Lib; -- Root package
>>
>> package Lib.Feat_1; -- Some feature
>>
>> package Lib.Feat_2; -- Another feature
>>
>> private package Lib.Impl; -- Things I want to keep secret,
>> conceptually they're in the private part of Lib IIUC.
>>
>> Am I right that it is impossible for Feat_1 and Feat_2 to communicate
>> using something that's private in Lib or Lib.Impl? That would mean
>> exposing those private types in their respective public parts, which
>> is a no go.
> 
> Lib.Feat_1 & 2 can see the private part of Lib, and the public part of
> Lib.Impl.
> 
> What's wrong with putting stuff in the public part of Lib.Impl? No one
> outside Lib can see it.

in Lib.Feat_1, doing a "with Lib.Impl" results in error
"current unit must also be private descendant of Lib".

I can do (in Feat_1) a "private with Lib.Impl", but then I can use these 
things only in private parts/body of Lib.Feat_1, which are also out of 
bounds for Lib.Feat_2, and viceversa.

Finally, I can make Lib.Impl not private and then it's just inelegant, 
since clients gain access to these declarations. Which is not a big 
issue, but is kind of a public pollution. This is basically what I'm 
doing now with Lib.Feat_X.Impl regular packages.

Thanks,
Álex.