Re: To check or not to check for NULL?

From:

Mike <mikes3959@yahoo.com>

Newsgroups:

comp.lang.java.programmer

Date:

Thu, 25 Sep 2008 19:25:20 -0700 (PDT)

Message-ID:

<81893bb1-aa4f-4f7a-877e-e9469680da53@g17g2000prg.googlegroups.com>

Joshua,

If you want to get the out of memory case too, you'll have to catch
OutOfMemoryError too. But I don't recommend trying to catch that since
too many things can go wrong.

So don't catch it (the Error- OutOfMemoryError ) all? And why would I
need to catch the exception as the other person suggested? I thought
new operator throws an Error, not an Exception. I'm not sure why Hakan
suggested catching an Exception.

On Sep 22, 1:39 pm, Joshua Cranmer <Pidgeo...@verizon.invalid> wrote:

Hakan wrote:

The obvious answer seems to be

try

{
JButton button = new JButton("test");
}
catch (Exception e)
{
System.out.println("Error Message");
}

If you want to get the out of memory case too, you'll have to catch
OutOfMemoryError too. But I don't recommend trying to catch that since
too many things can go wrong.

Also, you will generally only need to catch the checked exceptions, at
which point the compiler will complain if you don't catch.

--
Beware of bugs in the above code; I have only proved it correct, not
tried it. -- Donald E. Knuth