This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: catch(...) and forced unwind
- From: Jason Merrill <jason at redhat dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, rth at redhat dot com, mark at codesourcery dot com, drepper at redhat dot com, jakub at redhat dot com, ncm at cantrip dot org, dave at boost-consulting dot com, wekempf at cox dot net, fjh at cs dot mu dot oz dot au
- Date: Sat, 13 Dec 2003 01:54:55 -0500
- Subject: Re: catch(...) and forced unwind
- References: <xypwu91ofvf.fsf@miranda.boston.redhat.com><20031212183754.13f4864b.bkoz@redhat.com>
On Fri, 12 Dec 2003 18:37:54 -0600, Benjamin Kosnik <bkoz@redhat.com> wrote:
>>I see three ways to fix this:
>>
>>1) automatically rethrow cancellation.
>>2) explicitly rethrow cancellation--this would require some way to catch it
>> specifically, but we really ought to have that anyway.
>
> What about
>[...]
> Ie, a __cancellation_handler that could be set to either rethrow,
> continue, or abort?
That seems plausible to me. I think that #2 would still be appropriate.
Jason