C# Cannot Jump Out Of The Finally Block
Hit me up on Twitter if you want to discuss it further. The only branching opcode out of a finally is ‘endfinally‘, which jumps to the end of the finally block. How does the IL look like that IronPython generates? Why had Dumbledore accepted Lupin's resignation?
It is particularly dodgy in C++ of course due to the amusing C++ double fault behaviour, where if you throw from a destructor during an exception unwind, std::terminate is called and Tags Compilers & Languages Comments (4) Cancel reply Name * Email * Website .NET Junkie says: December 17, 2007 at 3:39 am I'm very curious. On the other hand, if you add a catch statement and rethrow the exception, you lose the information: the exception you re-throw in the catch block will now refer to the This is a huge advantage when debugging in order to determine where the exception was initially thrown, especially when you have lots of function calls inside your try block. anchor
Martijn van der Woud Mar 23, 2011 at 1:54 PM 10 Comments @Ben, @JulianI just did a quick check: it turns out that cfrethrow DOES preserve the original call stack info, Could I work as a Professor in Europe if I only speak English? Site Copyright © 2007 CodeBetter.Com Content Copyright Individual Bloggers