EXIT_ON_CLOSE

[chandrima bhat]

JFrame f;
f.setDefaultCloseOption(JFrame.EXIT_ON_CLOSE);

I wrote a program using the above code, but its giving errors. Can anyone help me with a correct way of setting setDefaultCloseOption in Java?

[Stuart Gray]

Well it helps if you can post the exact error message you are getting. However in this case I imagine the problem is that you haven't initialised f. The variable f is still null because you haven't called the JFrame constructor, you have only defined it as being a JFrame. You cannot call any methods on a null variable. Change the code to this:

JFrame f;                      // Variable declaration (f is still null)
f = new JFrame("Foo");         // Variable instantiation (f no longer null)
f.setDefaultCloseOption(JFrame.EXIT_ON_CLOSE);

[magic zha]

I think it must be:
JFrame f = new JFrame();
f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);

[miguel lisboa]

cant see the diference

[Stuart Gray]

There is no difference. The reason I kept the first two lines separate in my example was to stress the difference between variable declaration and initialisation.

[miguel lisboa]

of course

perhaps magic didnt want a title for the frame

[Ernest Friedman-Hill]

Miguel and Stuart are correct; splitting the declaration into two lines doesn't change the meaning at all, and in fact the compiler will very likely emit the identical bytecode in both cases.

Since we're quibbling over small details, however, I can't help but remark that Stuart's comment on the first line that "f is still null here" isn't quite right. f's value at that point is undefined; if you tried to read the value, the compiler would reject the code because f hasn't been initialized. If f were a member, then it would be automatically initialized to null, but that's not the case for locals.

[Stuart Gray]

Yep, spot on Ernest - thanks for that