Possible Duplicates:
Conditions when finally does not execute in a .net try..finally block
In C# will the finally block be executed in a try, catch, finally if an unhandled exception is thrown?
http://en.wikipedia.org/wiki/Comparison_of_C_Sharp_and_Java#Finally_Blocks_and_Uncaught_Exceptions states that the finally block doesn’t always run. That’s wrong, right?
The ECMA standard for the CLI (from which C# derives its exception features) states that exceptions are handled in a two-pass search of the stack.[13] The first pass attempts to locate a matching catch block, and terminates the program if none is found. Only if a matching catch block is found does the second pass execute, which runs the intervening finally blocks. This allows the problem to be diagnosed without the program state first being modified by the finally blocks; it also eliminates the risk that finally blocks may have undesirable side-effects when the program is in an unknown state (such as corruption of external data, or throwing further exceptions).
But, I don’t need a catch to finally execute:
static void Main()
{
try { throw new Exception(); }
finally
{
Console.WriteLine("1");
}
}
I notice that no one has actually answered your question, which is “is this text correct?”
No, it is not correct, in that it omits an important point.
The relevant portion of the CLI specification which it fails to quote is section 12.4.2 of Partition I, which states:
Now, as others have noted, there are some subtleties here. Notice that the specification clearly calls out that the finally is executed when the block exits. If the program is terminated by a failfast, by a stack overflow, or by someone pulling the power cord out of the wall, then the block never exits! The program could be terminated before the block exits, and therefore the finally would not run.