P99_CATCH P99_FINALLY P99_RETHROW P99_THROW P99_THROW_ASSERT P99_THROW_CALL_NEG P99_THROW_CALL_NEGATE P99_THROW_CALL_NOT_ZERO P99_THROW_CALL_RANGE P99_THROW_CALL_RANGE_ARG_0 P99_THROW_CALL_RANGE_ARG_1 P99_THROW_CALL_RANGE_ARG_2 P99_THROW_CALL_RANGE_ARG_3 P99_THROW_CALL_RANGE_ARG_4 P99_THROW_CALL_THRD P99_THROW_CALL_VOIDP P99_THROW_CALL_ZERO P99_THROW_ERRNO P99_TRY

P99_FINALLY #define P99_FINALLY Value: P00_FINALLY \ P00_BLK_AFTER(p00_unw ? P99_RETHROW : P99_NOP) Designate a block that is executed regardless of the exceptions that were encountered in the corresponding try block. Remarks If the finally clause was reached via the catching of an exception, the unwind of P99_TRY and P99_UNWIND_PROTECT blocks will continue. Otherwise execution will resume normally after the P99_FINALLY clause. A typical use pattern will be as follows: P99_FINALLY { // do some cleanup } // continue only if no exception had been caught See also P99_TRY P99_CATCH Warning Utilities that change control flow in an unexpected way may result in the loss of some modifications that are effected on variables. A modern compiler should tell you when you are in such a situation. If it is the case you'd have to declare the variable in question with the volatile qualifier. For an explanation see P99_UNWIND_PROTECT. Definition at line 630 of file p99_try.h.