|
Boost : |
From: Gennadiy Rozental (gennadiy_at_[hidden])
Date: 2002-08-18 12:29:58
> Thank you for the information. A helper header might be nice, though
> you might just add a macro like BOOST_CPP_MAIN to execution_monitor.hpp,
> which is reminiscent of the old system. Either solution would be fine
> by me.
After some consideration I see following two chooses:
1. I could try completely mimic Boost.Test V1 interface/functionality.
This solution includes:
a. Introduce boost/test/cpp_main.cpp, which in fact will be forwarding
header that includes
boost\libs\test\src\cpp_main.cpp and
boost\libs\test\src\execution_monitor.cpp
b. Make test_tools.hpp to handle BOOST_INCLUDE_MAIN (or some other more
descriptive name).
If BOOST_INCLUDE_MAIN is defined test_tools will implement some
limited lightweight functionality
similar to what Boost.Test v1 was doing.
This solution could be deprecated in a future, when it is not used anymore
2. I could introduce 2 new headers to support online (no library) testing
a. boost/online/prg_exec_monitor.hpp
This header will include
boost\libs\test\src\cpp_main.cpp and
boost\libs\test\src\execution_monitor.cpp
b. boost/online/test_exec_monitor.hpp
This header will include everything current online_test is including.
This solution could be permanent. It will work and support the same set of
features as offline version.
> Ron
Comments?
Gennadiy.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk