Be the Compiler

[Ashwin Sridhar]

Hi,

The following code snippet would help java-novice. wear the compiler's hat and say the output for the code snippets

1.

     try{
     //some code
     return;
    }finally{

    }
    

2.

     try{
     //some code
     System.exit();
    }finally{

    }
    

Try and tell in which cases the code in finally block will be executed

[anirudh jagithyala]

the code in the first case executes the finally block


try{
//some code
return;
}finally{

}

[Ashwin Sridhar]

yes. only the first one executes finally

[Mike Simmons]

Which might mean something if there were any code in the finally block. Since there isn't, it seems a poor example to discuss.

Also, "be the compiler" has nothing to do with this. The compiler has no idea what "System.exit()" does - it just knows it's a method that can be called with the appropriate bytecode. It's the JVM that determines, at runtime, that System.exit() results in shutting down without executing finally.

[Matthew Brown]

Mike Simmons wrote:The compiler has no idea what "System.exit()" does - it just knows it's a method that can be called with the appropriate bytecode.

Which is why

System.exit();
System.out.println("Do something");

will compile, but

return;
System.out.println("Do something");

will complain about unreachable code.