Should setAccessible be part of Java or not? (was Re: It's not too late for access control)

[Jochen Theodorou]

On 14.07.2016 17:54, mark.reinhold at oracle.com wrote:
> 2016/7/14 5:35:25 -0700, Andrew Haley <aph at redhat.com>:
>> At Red Hat we have many Java programmers.  We also have many customers
>> who are Java programmers.  I am trying to persuade people to try out
>> JDK 9 in order to give us the feedback we need to ratify the JDK 9
>> specification.  But you know where this is going: the changes to
>> Jigsaw which we need are TBD, but with an assurance of "I think we'll
>> be able to work something out."  This is a tough sell for me.
>
> Is this any different than the usual chicken-and-egg problem of
> live software development?  Much of Jigsaw is still in flux as we
> work through issues in both the specification and the implementation.
> If you have specific suggestions about how we could make it easier to
> persuade people to try JDK 9 then I'd like to hear them.
>
> Also, nobody is asking you, or anyone else, to take anything on faith.
> We are -- and long have been -- asking for feedback, both practical
> feedback based on running existing code against EA builds and design
> feedback from developers of all skill levels.

What I would wish for at this moment is a document explaining the 
runtime aspects of the module system, including limitations reflection 
and normal method calls, as well as things like layers / runtime 
generated modules - as well as the methods to be used to create and 
change these. I don´t anything JLS ready here and just the behaviour of 
the one of the latest releases is also good. I cannot give feedback on a 
design I do not know. Because maybe some frameworks are content with the 
compile time side of this, I am not.

bye Jochen