Re: Visibility issue

[Daniel <danielnorberto@gmail.com>]

El viernes, 11 de septiembre de 2020 a las 16:23:26 UTC+2, Jeffrey R. Carter escribió:
> On 9/11/20 12:37 PM, Daniel wrote: 
> > 
> > package Library.Users is 
> > type User_type is tagged with private; 
> > procedure foo_public (S: User_Type); 
> > private 
> > type User_Type is tagged with record 
> > hide_content_to_user : Natural; 
> > end record; 
> > function Access_to_hide_content return User_type; 
> > end Library.Users; 
> > 
> > private with Library.Users; 
> > package Internal_Library_Implementing is 
> > -- Some internal public developer stuff 
> > private 
> > --Here I want to get access to User_Type hide content. 
> > end Internal_Library_Implementing; 
> > 
> > I've tried using "private with" but gnat says the next: 
> > move subprogram to the visible part (RM 3.9.3(10)) 
> > private function with tagged result must override visible-part function 
> > 
> > Compiler says Im forced to make all private User_type functions public. 
> > So, are there more ways to see the hided content of this tagged type without extending the type itself in a child package? I needed to see this content outside of Library package.
> The private part is only visible to the body and to child pkgs. So if you declared 
> 
> private package Library.Users.Internal_Implementation is 
> 
> then it will be able to see the private part of Library.Users. Because it's a 
> private pkg, it cannot be used by clients. 
> 
> -- 
> Jeff Carter 
> "You couldn't catch clap in a brothel, silly English K...niggets." 
> Monty Python & the Holy Grail 
> 19

I was trying to separate the code in two hierarchies packages, one package for an API and other package for internal implementation.
IT's difficult to put the implementing details on the API "fake child" because I will need a lot of dependencies from Internal packages hierarchy.

It could be possible to use other solution different that put implementing details on API packages?