Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I recently made the statement to a colleague that:
NullReferenceExceptions should never be explicitly caught
I used the word never…. hmmm. I’ve never seen a appropriate use case myself for catching them but I wanted to check if anyone else has?
Never is such a strong word after all…..
It depends on why; see Eric Lippert’s blog entry. If they are ‘boneheaded exceptions’, then no – just fix the calling code. In the rare case that they are ‘vexing exceptions’ (i.e. the code you are calling has traps that are hard to avoid), then I guess you’d have to.