Re: Exception Specifications

Keith Halligan wrote:
> I'm a bit unsure about the following behaviour with exception
> specifiers in C++ functions
> 
> 
> Here's some sample code:
> 
> #include <exception>
> 
> class Sy***ception { };
> 
> void f( ) throw (Sy***ception)
> {
>     throw std::exception();
> }
> 
> 
> int main()
> {
> 
> }
> 

Calling f() should result in std::unexpected being called ...

[http://www.devx.com/tips/Tip/15140]
The Standard Library defines a function called std::unexpected() which
is invoked when a function throws an exception not listed in its
exception specification. std::unexpected invokes a user-defined function
that was registered by std::set_unexpected. If the user hasn't
registered such a function, unexpected() will invoke std::terminate(),
which in turn calls abort() and terminates the program. (...)

Exception specifications are apparently evil:
http://www.gotw.ca/publications/mill22.htm

br,
Martin

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