Re: Giving a package specification access to the private types of another package

["Grein, Christoph" <christoph.grein@eurocopter.com>]

> Grein, Christoph wrote:
> > This is indeed the perfect design for your problem.
> > 
> >>I think this is what I have done - and it works. My code is equivalent
> >>to the example below. This works and seems to be the best way to do it.
> >>
> >>package B is
> >>   procedure Proc_B;
> >>private
> >>    type Private_Type is new Integer;
> >>end B;
> >>
> >>with B.A;
> >>package body B is
> >>   procedure Proc_B is
> >>      Temp: Private_Type;
> >>   begin
> >>      A.Foobar(Temp);
> >>   end;
> >>end B;
> >>
> >>private package B.A is
> >>   procedure Foobar(Temp: in Private_Type);
> >>end B.A;
> >>
> >>package body B.A is
> >>   procedure Foobar(Temp: in Private_Type) is
> >>   begin
> >>      null;
> >>   end;
> >>end B.A;
> 
> Perfect? That's a bit strong. It's a good design, but as given, I think 
> that putting Foobar in B (perhaps with "is separate") is as good.

I beg to differ. For this tiny example, you're right. But IIRC, the OP said that 
his package B.A was quite big and held a big part of the implementation stuff of 
B. Then child packages are the "perfect" design because you can split one big 
body (B) is several smaller children dedicated to specific subproblems.