I use Java examples in this book. I find that Java tends to be easy for most object-oriented programmers to read. I�ve gone out of my way to not use fancy Java features, so whether you code in C++, C#, Visual Basic .NET, Python, Ruby, Smalltalk, or some other object-oriented language, you ought to be able to understand the Java code in this book.
Fowler's refactoring book also contained quite a lot of code examples. I believe it's essential for the kind of refactorings he described. I haven't seen Josh's book yet so I can't really say how much code it has in proportion to UML diagrams.
Ralph Johnson (one of the authors of Design Patterns) recently noted tha the refactorings in my book could easily be called patterns or refactorings. So I like to think that the book is about both refactoring and patterns. I certainly include lots of discussions about pattern implementations and competing patterns -- though I don't go into the detail found in the Design Patterns Implementation Notes.
The book does contain a LOT of code. The code is written in Java. There are also plenty of UML 2.0 diagrams. As I said in the book, I find that most C#/C++/OO developers can understand the code (we've tested it on a wide variety of folks in our workshops).
Author of <a href="http://www.amazon.com/exec/obidos/ASIN/0321213351/ref=jranch-20" target="_blank" rel="nofollow">Refactoring to Patterns</a>
Joined: Jan 08, 2004
mr.Joshua Kerievsky, could you please introduce yourself ? do you wrote this book with developer view ? thank you !
Joined: Nov 07, 2003
my book could easily be called patterns or refactorings
Will you rename your book in the next edition?
In addition, did you cover fundemental concepts of refactoring in your book?