When you return from try block, the return value is stored on the stack frame for that method. After that the finally block is executed. Changing the value in the finally block will not change the value already on the stack. However if you return again from the finally block, the return value on the … Read more
In your example, it doesn’t make a whole lot of difference. Picture this, though: try { Console.WriteLine(“Executing the try statement.”); throw new NullReferenceException(); } catch (SomeOtherException e) { Console.WriteLine(“{0} Caught exception #1.”, e); } finally { Console.WriteLine(“Executing finally block.”); } Console.WriteLine(“Executing stuff after try/catch/finally.”); In this case, the catch won’t catch the error, so anything … Read more
Also if you’re using Java 7, you can use a try-with-resources statement: try(BufferedReader r = new BufferedReader(new InputStreamReader(address.openStream()))) { String inLine; while ((inLine = r.readLine()) != null) { System.out.println(inLine); } } catch(IOException readException) { readException.printStackTrace(); }
The means of accomplishing this that I’ve seen require an extra method: public static void MyMethod() { using (var scope = MyScopedBehavior.Begin()) { //Do stuff with scope here scope.Complete(); // Tells the scope that it’s good } } By doing this, your scope object can track whether it’s disposing because of an error, or a … Read more
The resource gets closed before catch or finally blocks. See this tutorial. A try-with-resources statement can have catch and finally blocks just like an ordinary try statement. In a try-with-resources statement, any catch or finally block is run after the resources declared have been closed. To evaluate this is a sample code: class ClosableDummy implements … Read more
The use of continue in a finally-clause is forbidden because its interpretation would have been problematic. What would you do if the finally-clause were being executed because of an exception? for i in range(10): print i try: raise RuntimeError finally: continue # if the loop continues, what would happen to the exception? print i It … Read more
It can be done totally non-hackily like this: def function(x,y,z): if condition1: blah elif condition2: blah2 else: return False #finally! clean up stuff. In some ways, not as convenient, as you have to use a separate function. However, good practice to not make too long functions anyway. Separating your logic into small easily readable (usually … Read more
The most useful case is when you need to release some resources : InputStream is = … try { //code… } catch (Exception e) { //code… } finally { is.close(); } More generally, you use it when you want to be sure your code is executed at the end, even if there was an exception … Read more
I think there’s one key misunderstanding: You either have someone who wants “success and finally”, or “success and error” but none wants the 3 of them. This isn’t entirely true. Each Observable can send zero or more next notifications and one error or complete notification but never both. For example when making a successful HTTP … Read more
Yes, the language spec defines that “2” is the result. If a VM does it differently, it’s not spec-compliant. Most compilers will complain about it. Eclipse, for example, will claim that the return block will never be executed, but it’s wrong. It’s shockingly bad practice to write code like that, don’t ever do it 🙂