From: David Abrahams (dave_at_[hidden])
Date: 2006-12-18 16:47:20
Anthony Williams <anthony_w.geo_at_[hidden]> writes:
> "Gennadiy Rozental" <gennadiy.rozental_at_[hidden]> writes:
>> "Roland Schwarz" <roland.schwarz_at_[hidden]> wrote in message
>>> Gennadiy Rozental wrote:
>>>> Heh, I don't really like putting this kinda cludge into Boost.Test code.
>>>> if no one sees any alternatives go ahead
>>> If it was only about the threading lib, I have no problems of doing this
>>> just for this one library. But what about the others?
>>>>> Btw.: Do you have anything to say about my asynch-exeptions question?
>>>> Umm, I must've missed it. What was it?
>>> The test lib is being built with <asynch-exeptions>on. However the
>>> default for release builds is synchronous exceptions on.
>> This is plain wrong. build with msvc compiler require async exception
>> support to be enabled for Boost.Test to work properly.
> Huh? Why? Do you use Windows-native Structured Exception Handling? I thought
> that was the only reason for allowing async exceptions. Am I misunderstanding
Yes, the Test library uses it to catch program bugs like invalid
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk