Re: Exception Specifications

Jon wrote:
> On May 2, 4:43 am, Keith Halligan <keith.halli...@[EMAIL PROTECTED]
> 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();
>>
>> }
> 
> I may be wrong, but I believe that this code should fail to compile.
> The exception specification for f() indicates that it will throw
> objects only of type Sy***ception.  class Sy***ception is not derived
> from std::exception so throwing an object of class std::exception
> would violate the exception specification.
> 

No, the compiler should compile it because there is no error until f()
is called, and even then there is a well-defined action to be carried
out (call unexpected()) and so the code is still not erroneous.


-- 
Note that robinton.demon.co.uk addresses are no longer valid.

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