This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: EH in C (was: Re: (lack of) Thread-safe exceptions on AIX (gcc-2.95.1)
- To: llewelly at 198 dot dsl dot xmission dot com
- Subject: Re: EH in C (was: Re: (lack of) Thread-safe exceptions on AIX (gcc-2.95.1)
- From: Richard Henderson <rth at cygnus dot com>
- Date: Tue, 1 Feb 2000 00:19:42 -0800
- Cc: Bill Tutt <rassilon at list dot org>, gcc at gcc dot gnu dot org
- References: <Pine.LNX.3.95.1000131231310.24607A-100000@lima.mudlib.org> <Pine.LNX.4.10.10002010018280.9063-100000@198.dsl.xmission.com>
On Tue, Feb 01, 2000 at 12:31:21AM -0700, llewelly@198.dsl.xmission.com wrote:
> This is what catch(...) { throw;} is for. It works just like finally.
No it doesn't -- __finally *always* runs, whether an
exception is thrown or not.
r~