Lifting the restriction on the number of public classes per file
maurizio.cimadamore at oracle.com
Tue Nov 27 10:29:08 UTC 2018
On 27/11/2018 02:04, John Rose wrote:
> In source code the simple names can be obtained by using an import
> which mentions NH: `` import pkg.NH.* ``. So there's no great
> advantage to having the top-level names (package members) instead
> of the nested names (class members). Maybe there's some advantage
> in having reflection avoid mention the "NH$"?
I would add javadoc to the list of things that end up being suboptimal
when using a nested hierarchy. Again, not a game changer, but mentioning
here for completeness.
More information about the amber-spec-experts