Somewhere in the E.U., le 25/02/2005 Bonjour Gennadiy In article <cvlaol$u6o$1@sea.gmane.org>, "Gennadiy Rozental" <gennadiy.rozental@thomson.com> wrote:
Hi, Hubert
For some reason I couldn't locate message to respond, but here is reply to your last post:
Well, actually, I am held up at the moment by what seems to be internal Boost.Test problems.
I checked in a few days ago some modifications to the special functions tests, which take into account the modifications to the BOOST_CHECK_PREDICATE macro, but compilations still fails (Xcode 1.5):
1. You are using unit_test_ex.hpp. I forgot to remove this header. We don't need it anymore. Boost .Test now works with boost::function out of the box without any extra support. Just use unit_test.hpp
OK.
2. I noticed that your test could benefit from BOOST_TEST_TEMPLATE facility. I spend some time and look on attached version that do the trick. Fell free to use it if you want.
I will definitely use it, it is a very nice addition to the tools. It would also help if you added the construct you wrote ----------------------------------------------------------------------- template<typename T> struct string_type_name; #define DEFINE_TYPE_NAME(Type) \ template<> struct string_type_name<Type> \ { \ static char const * _() \ { \ return #Type; \ } \ } ----------------------------------------------------------------------- to a common header, as I believe I am not the only one who would benefit from it! BTW, what now replaces unit_test_log ?
3. Usually It's not good idea to do ant thing from within init_test_suite function. This code is not guarded and should only be used for test tree creation.
Gennadiy
OK. Merci Hubert Holin