Anthony Williams <anthony_w.geo@yahoo.com> writes:
"Gennadiy Rozental" <gennadiy.rozental@thomson.com> writes:
"Roland Schwarz" <roland.schwarz@chello.at> wrote in message news:4582E105.4050205@chello.at...
Gennadiy Rozental wrote:
Heh, I don't really like putting this kinda cludge into Boost.Test code. But 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 something?
Yes, the Test library uses it to catch program bugs like invalid pointer dereferences. -- Dave Abrahams Boost Consulting www.boost-consulting.com