From: David T. <dav...@cl...> - 2005-09-19 08:01:49
|
Am 15.09.2005 um 18:29 schrieb Wojtek Narczynski: > David Teran wrote: > > >> As last time with the logging discussion, you simply don't get >> the point. >> > > Are you suggesting that I am a dummy? > No, thats not the case. I simply say its a deja vue and kind of funny. > > > The check for null should be there exactly because I can imagine > calling this method with a null in one special situation: bug. I am > not interested in performance optimization of this situation. I am > interested in detecting the bug early. > yes, but i prefer checking the bug before, not here in this method. Its a bug in -your- code so check it there. > This way you don't avoid NullPointerException, you merely postpone > the problem to a point where the root cause of the bug is harder to > track down. > Your fears of exception are groundless. They are a valuable if used > properly, which isn't that hard. > This is completely a discussion about programming style, yours differs from mine, its not a discussion about 'better' its simply different. regards, David |