From: Cliff Green (cliffg_at_[hidden])
Date: 2005-05-06 15:38:32
Silly me - I should have looked in the Boost.Test Open
Issues page a couple of days ago instead of wasting my
time trying to solve some multi-threading problems in my
own code. So a couple of enhancement requests (for
Gennadiy, or appropriate person):
1. Please state clearly in the Boost.Test documentation
that it is not thread-safe. I looked all through the pages
(both the current release and the 1.31 release) but the
only place I find mention of thread-unsafety is in the
Open Issues page. The FAQ page would also be a good place
to mention Boost.Test thread-unsafety, besides the main
page (and places like Usage Recommendations, Examples,
Compilation, etc).
2. Please consider adding thread-safeness to the
Boost.Test libraries. I know this is not a simple request,
and there may be other priorities ... but many of my (and
my team's) unit tests are multi-threaded, and it's a shame
to not be able to use Boost.Test (or even know which, if
any, parts are thread-safe). It's a nice testing
framework, IMO. Note that I don't need the whole library
itself to be threaded, just to be able to do things like
BOOST_MESSAGE and BOOST_EQUAL within my own testing
threads. (I'll offer whatever help I can provide, within
the constraints of my available time.)
Many thanks!
Cliff