Having worked on a number of legacy applications over the years that are written in an OO programming language (Java) but are not really OO applications, I would like to ask of your book discusses any refactorings that may help guide us away from this "OO language, procedural design" practice that is so often found.
The book doesn't specifically go though any examples of how to refactor legacy code, but there are several areas where I discuss using wrappers to encapsulate code that is not object-oriented or system dependent.
Thanks,
Matt
Matt Weisfeld
Make yourself as serene as a flower, as a tree. And on wednesdays, as serene as this tiny ad:
a bit of art, as a gift, that will fit in a stocking