:-)
Vincenzo
Joachim Draeger wrote:
Vincenzo Gianferrari Pini wrote:
BTW: I have often seen NPE *bugs* in debug messages, that appeared
magically when the costumer has turned on *de*bugging. :-) This could
avoided by putting a try/catch block around...
Im against this.. Even if the NPE is in the debug message it should not
catched. IMHO thats a bad practice.. NPE should fixed not "catched" ;-)
Norman is totally right.
We should notice that the NullPointerException class is on purpose a
subclass of RuntimeException, whose handling is not enforced by the
java compiler just because it is a "coding error" that, by
definition, can not be anticipated and should just be fixed when
found. It does not make sense to anticipate any possible
RuntimeException *locally* in any possible place surrounding
everything everywhere by try/catch blocks.
Sorry! I should have written:
<irony> This could avoided by putting a try/catch block around...
</irony>
Shame on me, I know it is bad style to use irony 1. in electronic
communication 2. in a language that is not ones first.
I was joking related to methods to blow up code.
Joachim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
