On 7/21/06, Sébastien Lorion <[EMAIL PROTECTED]> wrote:
Utility classes should be static
For utility classes, I draw the line at whether or not they have influence on the larger environment. If using them in tests relies on the environment to be in a specific state (existing files or not, etc.), then it's time to mock them out to isolate out the dependency on the environment. -- Brad Wilson http://www.agileprogrammer.com/dotnetguy/ "Constraints are liberating." - David Heinemeier Hansson (author of Ruby on Rails)
