This is the mail archive of the
mailing list for the GCC project.
Re: [3.3] Followup to C++ forced unwinding
Nathan Myers <firstname.lastname@example.org> writes:
> Many of the requirements observed by exception-safe code are
> fortuitously very similar to those for thread-safe code, so it is
> common practice to write libraries that are both exception-safe and
> thread-safe. Since exception-handling code is usually the least
> well-exercised part of any system, it is critical to keep it simple
> and transparent. Accommodating two different behaviors eliminates
That's a very good point.
The only special tool I would need for handling thread cancellation
exceptions, as a programmer writing exception- and thread-safe code,
is a C++ name for these exception types so that I can catch and handle