Re: Private area and child packages

[Jeffrey Carter <spam@spam.com>]

danmcleran@hotmail.com wrote:
> 
> But then how do I know when the access to the Implementation object
> goes out of scope? It seems to me that I need to either derive from
> Ada.Finalization.Limited_Controlled or define Something as a smart
> pointer to Implementation.

Yes, to manage memory the best approach is a controlled type. Smart 
pointers are good because they do reference counting and eliminate 
dangling references.

There doesn't seem to be any way to prevent a child package from making 
copies of access values if you decide to hide the implementation of a 
visible type in the package body.

-- 
Jeff Carter
"Ada has made you lazy and careless. You can write programs in C that
are just as safe by the simple application of super-human diligence."
E. Robert Tisdale
72