Exceptions...

[Adrian Yan]

1. try {
2. tryThis();
3. return;
4. } catch(IOException x1) {
5. System.out.println("exception 1");
6. return;
7. } catch(Exception x2) {
8. System.out.println("exception 2");
9. return;
10. } finally {
11. System.out.println("finally");
12. }
-----------------------------------------------------
Why the answer is:
"exception 1 finally"
I thought after hte first execption is caught, it would return.

[rob moreland]

the return command will not stop the finally clause from being run. Almost nothing will prevent it from being run.
I am assuming tryThis creates an exception.

[Vidya Selvaraj]

Exception being System.exit(0), right??

[Adrian Yan]

How can it be? If a return is called, the method should stop executing.

[rob moreland]

The point of the finally clause to take care of some important clean up, that MUST be done NO matter what. Here you make sure data is left in a consistent states, files properly closed etc.....
For this reason Java is written to make sure that it is run, almost always. The return command is not powerful enough to override this.
System.exit is however, which is why in most cases I don't think it should be used. good for small programs but dangerous for larger ones. Also if the finally clause throws an untrapped exception, the finally clause won't be run.

[ashwini srinivasan]

The finally block is always executed except when there is a
System.exit() call.