You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You say that "In pre-Java 9 world any public class was available everywhere and could be used by any other class". Preventing access to a class is often cited as one of the advantages of Java 9 modules. Do you know why the existingprivate keyword is not enough when willing to prevent usage of a class?
Beside this I often wonder why one would want to hide code in a world where 99% of dependencies come from open source projects!
The text was updated successfully, but these errors were encountered:
Thanks for your cheatsheet!
You say that "In pre-Java 9 world any public class was available everywhere and could be used by any other class". Preventing access to a class is often cited as one of the advantages of Java 9 modules. Do you know why the existing
private
keyword is not enough when willing to prevent usage of a class?Beside this I often wonder why one would want to hide code in a world where 99% of dependencies come from open source projects!
The text was updated successfully, but these errors were encountered: