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: <46C60C50.2080301@roguewave.com>
Date: Fri, 17 Aug 2007 15:00:00 -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>
In-Reply-To: 
 <C8506D6098A6F545BA3745D0CE359E83017D1F88@qxvcexch01.ad.quovadx.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Travis Vitek wrote:
>  
> 
>> Martin Sebor wrote: 
>>
>> Travis Vitek wrote:
>>> Martin,
>>>
>>> I'm not sure if you're aware, but I don't believe that the 
>>> destructors for stack objects inside the C functions will
>>> be called. I know that this is the case for MSVC7/8. This
>>> isn't an issue for your testcase, but it may be an issue
>>> for the functions invoked by __rw_once.
>> Interesting! I didn't know about this limitation. It's something
>> we need to keep in mind when writing the initialization functions.
>> Perhaps the solution will be to require the initialization function
>> to have the empty exception specification. That way we could rely
>> on the compiler to detect initialization functions that can throw.
>>
> 
> I just found out that the /Ehc flag enables the nothrow default
> for C linkage functions. So changing the /EHsc flag to /EHs will
> fix this for both VC7 and 8.

Do you happen to know if there's a #pragma that will let us select
the mode we need for just the one function?

Martin