[boost] Re: Re: [Test] Thread-safety

"Caleb Epstein" wrote:

I agree with Cliff and propose that this thread-safety (or thread-awareness) issue is best handled inside of the Boost.Test Test Tools macros themselves. I think the code that a user has to write to protect Test Tools macro invocations vs. the code that could be generated by the Test Tools doing their own protection might be meaningfully different. For example:

[snip]

Thoughts?

A test framework should stay as non-obtrusive as possible. Does thread safety in Boost.Test mean linking yet another *.cpp files or libraries? /Pavel