This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
The purpose of the book is spelled out on the back cover: to help programmers communicate with other programmers through their code. Wherever I found a common problem with several reasonable solutions, I picked the one that communicated most clearly. Many of the patterns have code examples, some from real code and some from invented examples.
Does that answer your question?
Kent Beck Three Rivers Institute
Author of <a href="http://www.amazon.com/exec/obidos/ASIN/0596007434/ref=jranch-20" target="_blank" rel="nofollow">JUnit Pocket Guide</a>
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Implementation Patterns --- Practical , case study oriented ?