Re: Private area and child packages

[danmcleran@hotmail.com]

tmoran@acm.org wrote:
> How about renaming Some_Package.Child_Package to
> Some_Package_Child_Package, ie, don't make it a child package.
> The usual reason for making something a child package is to allow it
> visibility into the parent, which is exactly what you don't want
here.
> So for what reason are you using the child package mechanism?
What I was wondering was how someone writing Some_Package can enforce
this on future package writers. I could obviously follow your
suggestion if I am the only developer writing code for a project. But,
if I want to hide implementation details from someone else who might
write a child package, I would need some mechanism to enforce this
information hiding.