[jsr294-modularity-eg] Nested superpackages
Bryan Atsatt
bryan.atsatt at oracle.com
Fri Apr 20 13:23:17 EDT 2007
Yes, but that is certainly a much simpler model. Do you think this is a significant restriction?
// Bryan
________________________________
From: jsr294-modularity-eg-bounces at cs.oswego.edu [mailto:jsr294-modularity-eg-bounces at cs.oswego.edu] On Behalf Of Glyn Normington
Sent: Friday, April 20, 2007 6:22 AM
To: JSR 294 Expert Group
Subject: [jsr294-modularity-eg] Nested superpackages
Must a nested superpackage be defined by the same class loaders as its parent (enclosing) superpackage?
If so, this would seem to put a restriction on the class names in a nest of superpackages: there must be no duplicates. This is a little surprising as it means unexported internals of a (nested) superpackage can cause problems depending on the content of the parent superpackage.
Glyn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20070420/b3d078ba/attachment.html
More information about the jsr294-modularity-eg
mailing list