Re: Visibility issue

[Daniel <danielnorberto@gmail.com>]

El viernes, 11 de septiembre de 2020 a las 13:51:39 UTC+2, Maxim Reznik escribió:
> You can try this way:
> package Library.Users is 
> type User_type is tagged with private;
> ... 
> end; 
> private package Library.Users.Implementation is 
> ...-- access User_Type internals 
> end; 
> 
> In Matreshka[1] we use another approach. We have a separate hierarchy of package for internals (in Matreshka.XXX packages) and a public API in League.XXX packages. However, nothing stops the user from use internal packages there. 
> 
> [1]: https://github.com/reznikmm/matreshka

I think that what I was doing is really close to your example: having two separates hierarchy. One for API just for type conversions and user interface, and other package hierarchy for internal implementing.
Let me use the same names as your example.
I need to access from Internal Matreshka packages to the private part of API tagged type. If im obligated to put the implement details in the child package of API, i will need also all the dependencies located in the Matreshka.XXX. That will make a mess of dependencies.