Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Be the Compiler

 
Ashwin Sridhar
Ranch Hand
Posts: 277
Flex Oracle Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

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

1.

2.

Try and tell in which cases the code in finally block will be executed
 
anirudh jagithyala
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
the code in the first case executes the finally block


try{
//some code
return;
}finally{

}


 
Ashwin Sridhar
Ranch Hand
Posts: 277
Flex Oracle Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
yes. only the first one executes finally
 
Mike Simmons
Ranch Hand
Posts: 3076
14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Bartender
Posts: 4567
8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
will compile, but
will complain about unreachable code.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic