Re: Exception Specifications

From:

Greg Herlihy <greghe@mac.com>

Newsgroups:

comp.lang.c++.moderated

Date:

Sat, 3 May 2008 06:13:28 CST

Message-ID:

<9e3a5aa6-8450-4495-b282-1abc3772bfae@c19g2000prf.googlegroups.com>

On May 2, 11:47 am, Jon <j.trauntv...@comcast.net> wrote:

On May 2, 4:43 am, Keith Halligan <keith.halli...@gmail.com> wrote:

I'm a bit unsure about the following behaviour with exception
specifiers in C++ functions

Here's some sample code:

#include <exception>

class SysException { };

void f( ) throw (SysException)
{
throw std::exception();

}

I may be wrong, but I believe that this code should fail to compile.

No. On the contrary, a C++ compiler is not allowed to report an error
with f()'s definition above: According to the C++ Standard:

"An implementation shall not reject an expression merely because when
executed it throws or might throw an exception that the containing
function does not allow." [?15.4/10]

The fact that exception specifications are enforced only at runtime in
C++ (instead of at compile-time when such checking would be useful) -
makes exception specifications too risky for most real-world C++
applications to adopt.

Greg

--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]