Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <46CB3C1C.3020905@roguewave.com>
Date: Tue, 21 Aug 2007 13:25:16 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software, Inc.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: svn commit: r565959 -
 /incubator/stdcxx/trunk/etc/config/src/EXTERN_C_EXCEPTIONS.cpp
References: <20070814224803.62DC81A981D@eris.apache.org>
 <C8506D6098A6F545BA3745D0CE359E83017D1B3B@qxvcexch01.ad.quovadx.com>
 <46C25484.3040604@roguewave.com>
 <C8506D6098A6F545BA3745D0CE359E83017D1F88@qxvcexch01.ad.quovadx.com>
 <46C60C50.2080301@roguewave.com>
 <7BDB2168BEAEF14C98F1901FD2DE6438D3EC3A@epmsa009.minsk.epam.com>
 <46CB2E24.50509@roguewave.com>
 <7BDB2168BEAEF14C98F1901FD2DE6438D3EC43@epmsa009.minsk.epam.com>
In-Reply-To: <7BDB2168BEAEF14C98F1901FD2DE6438D3EC43@epmsa009.minsk.epam.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Farid Zaripov wrote:
>> -----Original Message-----
>> From: Martin Sebor [mailto:sebor@roguewave.com] 
>> Sent: Tuesday, August 21, 2007 9:26 PM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: Re: svn commit: r565959 - 
>> /incubator/stdcxx/trunk/etc/config/src/EXTERN_C_EXCEPTIONS.cpp
>>
>>>   There's no #pragma for that, but we can compile all cpp 
>> files with 
>>> /Ehsc, and some set of specified files with /EHs.
>> Okay, that's something to consider. We'll have to see how 
>> pervasive the use of __rw_once() will be as soon as I'm done 
>> switching to it (so far I think it'll be needed in only a 
>> handful of places) and whether any of the initialization 
>> functions will potentially throw.
> 
>   I've just tried to declare and define __rw_once with throw(...)
> exception
> specification and compiler doesn't issues warning in that case.

Good to know! We still need to decide how to handle this in
the general case (for compilers that behave like MSVC, if
there are any) but we can certainly start using this extension
to silence the MSVC warnings.

> 
>> Btw., from the MSVC Exception Handling Model:
>> http://msdn2.microsoft.com/en-us/library/1deeycx5(VS.80).aspx
>> it looks like by default the compiler generates code that 
>> makes catch blocks catch structured exceptions (in addition 
>> the C++ kind). That's generally considered bad practice, but 
>> it may be relied on by user code for historical reasons. We 
>> need to be careful not to impose requirements on our users 
>> that would go against this historical practice (doing so 
>> could break working code).
> 
>   It was by default only in MSVC versions prior 7.0 (because
> the only asynhronous exceptions handling model was implemented.
> Since MSVC 7.0 they added synhronous exceptions handling
> model and this model is used by default.

Thanks for the clarification! I've also discovered it in the
docs since I sent my mail.

Martin