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

[news01+Steven.Murdoch@cl.cam.ac.uk (Steven Murdoch)]

In article <M_mJ9.53337$hK4.4591912@bgtnsc05-news.ops.worldnet.att.net>,
 "James S. Rogers" <jimmaureenrogers@worldnet.att.net> writes:
>You clearly have a poor organization. Try to think a bit more about
>modularity when designing packages. Either A and B should be
>merged into a single package, or pieces of A and B should be
>moved from one package to the other.

A has a large amount of code but a very small specification. It would
be correct to embed A in B, however this would make B very large.
By having A as a package, B can be fairly small. A has a distict purpose
(Memory Management) and I would like to isolate all of this in one file.

Other than merging A and B there is nothing that can be moved between
them and maintain correctness. A is used by B and by no other package,
all of the procedures in A are used by B.

Steven Murdoch.