August 2011
Intermediate to advanced
280 pages
6h 50m
English
The beaten path is the safest, but the traffic’s terrible!
I’ve discouraged shared mutability quite a few times so far in this book. You may ask, therefore, why I discuss it further in this chapter. The reason is quite simple: it’s been the way of life in Java, and you’re likely to confront legacy code that’s using shared mutability.
I certainly hope you’ll heavily lean toward isolated mutability or pure immutability for any new code, even in existing projects. My goal in this chapter is to help cope with legacy code—the menacing code you’ve soldiered to refactor.
Read now
Unlock full access