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.
hi all, just a couple of questions before uploading..... did anyone worry about the type of methods they were using and restrict it as much as possible ? Leaving most of the methods public (out of habit) and only the ones only used inside a class private Did anyone bother about changing signatures into friendly/protected ? Did anyone bother to overwrite toString or equals in most of the classes, as suggested by one of the suns design books. thanks for replies, friso
swimming certificate (A & B), shoelaces diploma, and some useless java ones.
I agree with Mark on when to use pulic/private. I did have some protected methods/references, because I used a Builder Pattern which uses inheritance to create different types of composites. My feelings, based on an application I wrote (that I still have to maintain) early in my career that had a lot of global identifiers, are that assume private on everything and then gradually ease the restiction until you have the right scope. Michael Morris
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction. - Ernst F. Schumacher
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