On Tue, 30 Jun 2009 14:50:54 +0200, Sanne Grinovero
I am building a util class to get some consistency, and plan to unit
test this extensively to make sure it throws understandable exceptions
for the most common mistakes (hey, I need a public no-args
constructor! / not implementing the X interface! / ...)
-> DRY, improve error messages.
Great idea. +1 from my side
Should I change all use cases I can find? I like consistency, not
I am also for consistency. If we are going to clean up the code we should
do it as good as possible. From my point of view there is also no problem
with the timing.