[jsr294-modularity-eg] hide otherwise exported classes
cierniak at google.com
Wed Apr 11 13:38:32 EDT 2007
(Changing the subject, so that we have a separate thread for each issue).
On 4/11/07, Eugene Vigdorchik <ven at jetbrains.com> wrote:
> Next it seems that having only the possibility to export classes/subpackages
> is not enough, it should be possible to hide otherwise exported classes.
> Thus already having a package in the superpackage the user should be able to
> hide a certain class in it without listing all the classes left explicitly
> in the superpackage.
Just to make clear, an example for this suggestion is (using syntax
made up for this email):
export package P;
hide class P.C;
is this correct?
It is an interesting proposal. However, as you will probably see in
future discussions, I have a general bias towards simplicity and in
this particular case, I don't see enough value in allowing this extra
complication. While it might make your life easier in some cases, I
see a danger that understanding what is really exported might suffer
(this is of course just based on my intuition).
More information about the jsr294-modularity-eg