On 10/03/2016 10:15 AM, Rafael Winterhalter wrote:
[...] However, for the adoption process, I think it is crucial that non-modularized code behaves as it did before, i.e. that non-modularized code shows the same behavior when its run on a Java 9 VM.
I agree with the sentiment here however I disagree with the conclusion. I believe it is critical that existing code can be brought into modules without having to first rewrite all reflection/internal references/etc. These things should all be coverable by (a minimal set of) specific declarations to allow applications to be modularized even if they have "legacy"-flavored problems. Otherwise old code will be in a permanent bit-rotted state which it will be hard to escape from - especially large intertwined code bases.
-- - DML
