[basic-improvements] try/finally support for c/c++ - more tests

[Mark Mitchell]

--On Thursday, November 07, 2002 08:52:37 PM -0500 Jason Merrill 
<jason@redhat.com> wrote:

> On Thu, 07 Nov 2002 17:26:38 -0800, Mark Mitchell <mark@codesourcery.com>
> wrote:
>
>>> That's why the proposal is about __try/__finally only, not __except
>>> where it is e.g. not clear at all what happens if you throw in C++
>>> and __except control expression returns -1.
>>> At least from what I read in MSFT docs on the web, their __try/__finally
>>> matches Aldy's patch.
>>
>> Except that it also handles asynchronous exceptions, which ours doesn't.
>> Where we'd get a SIGFPE you get a structured exception in Microsoft's
>> stuff.
>
> That has nothing to do with the semantics of try/finally, which just deals
> with cleaning up after whatever exceptions do happen to be thrown.

This horse is pretty dang dead, but the point is that people will *expect*
that the construct behaves the same way as Microsoft's "structured
exception handling" stuff -- in every way.  Part of that is handling
SIGFPE type events.

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com