Boost logo

Boost :

Subject: Re: [boost] [test] Trunk broken: What happened to test_exec_monitor?
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2011-10-04 14:43:51

John Maddock <boost.regex <at>> writes:

> >> special_functions_test.cpp
> >> special_functions_test.cpp(16) : fatal error C1083: Cannot open include
> >> file: 'boost/test/test_case_template.hpp': No such file or directory
> >
> > This one was deprecated as well long time ago. I can put it back, but it's
> > empty. I'll reinstate it for now.
> Assuming that it really is empty, I removed those includes from Boost.Math,
> but now get:

Most of these issues are due to this test modules using 5+ years deprecated
interfaces, which I'd like to remove now. Since you never bothered to switch to
updated interfaces, they came up now.

> 'BOOST_MESSAGE': identifier not found

BOOST_MESSAGE is deprecated. Correct name is BOOST_TEST_MESSAGE.

> 'unit_test_framework': the symbol to the left of a '::' must be a type

unit_test_framework is deprecated. Correct name is unit_test

> A clean build still gives:
> boost::unit_test::callback0<struct boost::unit_test::ut_detail::unused>

That's ... strange. I removed the header which defines this template. I am not
sure how is it possible for you to observe this.

> BTW you can easily test these issues for yourself by building the Boost.Math

I'll do later tonight.

> tests - frankly all of my "boost time" the last few days has been taken up
> with chasing down Boost.Test issues

You can easily switch back your local trunk to version of Boost.Test from couple
weeks ago.

> - and I'm sure I'm not alone.

I actually hope that there are few instances of deprecated interfaces being
used. I did not hear any mention of them for a long time.

> Last time this happened - not that long ago as it happens -
> I rewrote a bunch of code
> to not use Boost.Test anymore. I now see that as a very wise move, even
> though there should be much better uses for my time.

We live in a same boat. We both need to do some development and we can't always
be in sync. For your development I'd recommend you to test against release
branch version of Boost.Test. I will not push my changes into release until full
regression test run is clear.

If you do not mind I can make changes tonight to your test modules so that they
compile, unless you insist you want to use deprecated interfaces.


Boost list run by bdawes at, gregod at, cpdaniel at, john at