Feature complete?

[Alan Bateman]

On 01/12/2015 14:42, Vitaly Davidovich wrote:
>
> Alan,
>
> What's the reason a new java/bytecode access modifier to indicate 
> module-private wasn't implemented? I agree that public not being 
> really public is a big wart.
>
In the Under the Hood talk then Alex touches on the topic as to why it 
isn't opt-in at the type level.

public != accessible will be a surprise at first but not hard to get 
used to. We've been able to all the frameworks and heavy users of 
core-reflection in the JDK (JMX, RMI, CORBA, JAX-* etc.) working as 
explicit modules without too much back strain.

-Alan