From: Gennadiy Rozental (gennadiy.rozental_at_[hidden])
Date: 2004-06-29 22:01:43
> I dare say that Boost.Test should avoid dependencies on boost
> libraries. I would suggest isolating the MPL dependencies even if
> that means re-implementing the parts that it uses. Boost.Test is
> special and avoiding cyclic dependency will help us not go insane.
> Joel de Guzman
At the moment Boost.Test directly depends on:
Actually MPL and Boost.Function dependency is not critical yet since it does
not affect library compilation and used only for extensions. But I
definitely is not going to reimplement all above headers.
Don't forget that Boost.Test among other things is standalone library and
in may have need for use some existent core components. I wanted to propose
to introduce macro BOOST_INTERNAL_TEST. If this macro is defined I will try
to ifdef out optional dependencies. Boost libraries authors may define this
symbol. Though In general I do not see anything wrong with Boost.Test
dependencies on other boost components unless it introduce loops: Boost.Test
depends on component that uses Boost.Test for unit testing. I believe it
resolvable by using different layers of Boost.Test or with macro proposition
In a near future I plan to use boost::optional, iterator_facade
boost::lexical_cast and probably boost::function and boost::bind. And I am
sure dependency keep grow. My only limitation is that it should work on all
platforms where we perform regression testing.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk