In addition to the several fine answers you already have here: there is a very important difference between an exception filter and an “if” in a catch block: filters run before inner finally blocks. Consider the following: void M1() { try { N(); } catch (MyException) { if (F()) C(); } } void M2() { … Read more
Yes, it is guaranteed (provided the exception is caught), down to the order in which the destructors are invoked: C++11 15.2 Constructors and destructors [except.ctor] 1 As control passes from a throw-expression to a handler, destructors are invoked for all automatic objects constructed since the try block was entered. The automatic objects are destroyed in … Read more
Consider what would happen if you were to return 1 inside the try block and return 0 inside the finally block… Your function would be trying to return two values! The combined options of try and catch are exhaustive in terms of control flow.
Why are Objects created within the try/catch block not in scope with the rest of the method? They are. Variables declared within the try/catch block are not in scope in the containing block, for the same reason that all other variable declarations are local to the scope in which they occur: That’s how the specification … Read more
It was added in Java 7. It’s called the try-with-resources statement. /edit Might as well throw this in here too. You can use the try-with-resources statement to manage Locks if you use a wrapper class like this: public class CloseableLock implements Closeable { private final Lock lock; private CloseableLock(Lock l) { lock = l; } … Read more
Declaring a variable as const requires you to immediately point it to a value and this reference cannot be changed. Meaning you cannot define it at one place (outside of try) and assign it a value somewhere else (inside of try). const test; // Syntax Error try { test = 5; } catch(err) {} On … Read more
Why is that bad? It’s no different conceptually than: void TrySomething() { try { } catch (ArgumentException) { HandleTrySomethingFailure(); } } void HandleTrySomethingFailure() { try { } catch (IndexOutOfRangeException) { } } Before you go over there and give him a piece of your brain (try the parietal lobe, it’s particularly offensive) , what exactly … Read more
For me, two try-catch blocks makes most methods too long. It obfuscates the intention if the method is doing many things. With two try-catch blocks, it’s doing at least four things, to be precise two cases for main flow (two try blocks) two cases for error handling (catch blocks) I would rather make short and … Read more
Yes, they will. using(SPWeb spWeb = spSite.OpenWeb()) { // Some Code } is equivalent to { SPWeb spWeb = spSite.OpenWeb(); try { // Some Code } finally { if (spWeb != null) { spWeb.Dispose(); } } } Edit After answering this question, I wrote a more in depth post about the IDisposable and Using construct … Read more