Brian’s Kindle Notes & Highlights

Effective Java, by Joshua Bloch

Note that a nonzero-length array is always mutable, so it is wrong for a class to have a public static final array field, or an accessor that returns such a field. If a class has such a field or accessor, clients will be able to modify the contents of the array. This is a frequent source of security holes:

Oops, have committed this error before. Use immutable Collections (some examples https://www.baeldung.com/java-immutable-list) instead?

07 Sep 18 · Flag

Robert

This is often used as a workaround. If you have an anonymous inner class that needs to modify a value — say, an int — of its enclosing method (but values accessed by an inner class must be final) a fr…

See Brian’s 34 notes & 87 highlights