This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
You can't, really. Unless you can test for an error condition before you even call the method. For example, if there's a chance that a reference is null, don't call ref.method() without first checking if ref is null:
Campbell Ritchie wrote:To go on from what MS said: that sort of thing is using Exceptions for flow control. In fact, you would be using the Exceptions as a substitute for if statements, which is by no means good design.
Um, I wasn't talking about using exceptions for flow control at all. I was talking about the opposite, using flow control to prevent exceptions. And I don't think anything that the original poster talked about implied using exceptions for flow control. Than again, I'm not sure what the original poster meant, if it wasn't what I said, so maybe they could explain the goal better.
Vinod Tiwari wrote:like Mike and Campbell explained it would not be a wise idea/design to put multiple checks to avoid the exception.
That sounds like the opposite of what I said.
Joined: Oct 13, 2005
I must have been un‑clear. I meant that throwing an catching Exceptions is akin to using exceptions for flow control. I thought that was what OP was asking about.
What you showed is, as you said, the opposite. Using the if (obj == null)… test is a way to prevent exceptions.