try-catch-finally

Why doesn't @try block work? It crashed the app, but it was supposed to be caught by the @try block. NSString* test = [NSString stringWithString:@"ss"]; @try { [test characterAtIndex:6]; } @catch (NSException * e) { NSLog(@"Exception: %@", e); } @finally { NSLog(@"finally"); } 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"

I'm studying for my test in Object Oriented Programming and I was wondering if there is any case what so ever that considering the following code: try { do something } catch (someException e) { } finally { do something } the finally block will not execute? Yes. If you crash the Java VM or otherwise muck things up via native code, cause the program to terminate, or loop/wait infinitely inside the try block. Those are the only three cases which will avoid executing the finally block. If you call System.exit(0) in the try . Or make something that makes the JVM quit or hang (like a deadlock).

I am trying to convince myself that actions taken in the finally clause happen before the function return (in the memory consistency sense). From the JVM specification , it is clear that within a thread, program order is supposed to drive the happens before relationship -- if a happens b in the program order then a happens before b . However, I have not seen anything explicitly stating that finally happens before return, so does it? Or, is there some way that the compiler could reorder the finally clause since it is simply logging. Motivating example: I have one thread fetching objects out of

I just had a pretty painful troubleshooting experience in troubleshooting some code that looked like this: try { doSomeStuff() doMore() } finally { doSomeOtherStuff() } The problem was difficult to troubleshoot because doSomeStuff() threw an exception, which in turn caused doSomeOtherStuff() to also throw an exception. The second exception (thrown by the finally block) was thrown up to my code, but it did not have a handle on the first exception (thrown from doSomeStuff()), which was the real root-cause of the problem. If the code had said this instead, the problem would have been readily

This question already has an answer here: Returning from a finally block in Java 5 answers Multiple returns: Which one sets the final return value? 7 answers Can we use return statement in finally block. Can this cause any problem? Returning from inside a finally block will cause exceptions to be lost. A return statement inside a finally block will cause any exception that might be thrown in the try or catch block to be discarded. According to the Java Language Specification: If execution of the try block completes abruptly for any other reason R, then the finally block is executed, and then