If any of the code in the try block can throw a checked exception, it has to appear in the throws clause of the method signature. If an unchecked exception is thrown, it’s bubbled out of the method. The finally block is always executed, whether an exception is thrown or not.
Finally always executes. That’s what it’s for, which means its return value gets used in your case. You’ll want to change your code so it’s more like this: function example() { var returnState = false; // initialization value is really up to the design try { returnState = true; } catch { returnState = false; … Read more
No, it’s not a bad practice. Putting return where it makes sense improves readability and maintainability and makes your code simpler to understand. You shouldn’t care as finally block will get executed if a return statement is encountered.
“Guaranteed” is a much stronger word than any implementation of finally deserves. What is guaranteed is that if execution flows out of the whole try–finally construct, it will pass through the finally to do so. What is not guaranteed is that execution will flow out of the try–finally. A finally in a generator or async … Read more
I had a REALLY hard time to track down a bug years ago that was caused by this. The code was something like: Object problemMethod() { Object rtn = null; try { rtn = somethingThatThrewAnException(); } finally { doSomeCleanup(); return rtn; } } What happened is that the exception was thrown down in some other … Read more
All work perfectly 🙂 NSString *test = @”test”; unichar a; int index = 5; @try { a = [test characterAtIndex:index]; } @catch (NSException *exception) { NSLog(@”%@”, exception.reason); NSLog(@”Char at index %d cannot be found”, index); NSLog(@”Max index is: %lu”, [test length] – 1); } @finally { NSLog(@”Finally condition”); } Log: [__NSCFConstantString characterAtIndex:]: Range or index … Read more
The big difference is that try…catch will swallow the exception, hiding the fact that an error occurred. try..finally will run your cleanup code and then the exception will keep going, to be handled by something that knows what to do with it.
If a finally block throws an exception what exactly happens ? That exception propagates out and up, and will (can) be handled at a higher level. Your finally block will not be completed beyond the point where the exception is thrown. If the finally block was executing during the handling of an earlier exception then … Read more
Yes, finally will be called after the execution of the try or catch code blocks. The only times finally won’t be called are: If you invoke System.exit() If you invoke Runtime.getRuntime().halt(exitStatus) If the JVM crashes first If the JVM reaches an infinite loop (or some other non-interruptable, non-terminating statement) in the try or catch block … Read more