On 13-02-19 01:53 AM, Gennadiy Rozental wrote:
Eric Niebler <eric <at> boostpro.com> writes:
There are a lot of tests broken on trunk because of this change. Grepping through Jamfiles under libs/, I find 75 references to boost_test_exec_monitor. Can you clean this up, or restore the broken functionality please?
This should be fixed now, but guys lets spend 5 minutes and change to use unit test framework. It's really just few line of code that needs to be changed.
Sadly, many boost libraries aren't actively maintained. If you really want to evolve your library in a non-backward-compatible way (and I don't dispute your right to do that, or begrudge you for it), then you should to have a plan for what to do with those libraries. You may have to make the necessary changes yourself. -- Eric Niebler Boost.org