Re: Exception Specifications

From:

Rolf Magnus <ramagnus@t-online.de>

Newsgroups:

comp.lang.c++

Date:

Fri, 02 May 2008 10:53:41 +0200

Message-ID:

<fvekql$i7t$02$1@news.t-online.com>

Keith Halligan wrote:

If I compile the code below on Solaris, Linux and AIX, I get the
program coring, causing the "std::exception" to be thrown back to the
runtime and the "catch (std::exception)" is not handled.

However if I run this on Windows (VC++6 and VC++8), the "catch
(std::exception") handler is used.

I know this is going a bit platform specific, but I'm just wondering
what the proper behaviour for C++ should be?

std::unexpected() should be called, which in turn calls the unexpected
handler, which by default (if you didn't specify another one) calls
std::terminate, which calls the terminate handler, which by default calls
abort().

I would expect the Unix platforms to have the correct behaviour as we
are invalidating the exception specifier so that should *not* be
allowed.

Yes. The whole point of exception specifications is that the caller can be
100% sure that the function does never throw any exception that is not
mentioned in the specification.