Author | Topic |
Location: Cabramatta, NSW
Registered: May 2002
|
Re: hey java buffs
|
Tue, 06 May 2003 05:51
|
|
HKSPete wrote on Tue, 06 May 2003 13:48 | Testing for null pointers like Nark says is a good safety measure. But no one puts stuff in a try block (not a loop) specifically for NullPointerException(s) though, just for the base Excepton and then print the stacktrace to see what the exception is.
Sorry to be anal, but the compiler will pick it up. And doing a try for a null pointer is just bad practise. I won't let any of my team at work do those kind of things (they are quite resourseful in their different types of bad programming practises techniques)
|
Depends on how everything is set up. Stuff like null pointers shouldn't create a stack trace if it's fixable.
I wouldn't put a try loop JUST to catch a NullPointerException, I'd just put the if blocks around it.
But sometimes you can fix it elegantly with a catch for null pointers. Like verify that the rest of the data is clean or even throw more exceptions for them to casade outward.
Really depends on your architecture.
|
|
|