[range] partial_workaround test
I remember that we agreed not to fail workaround tests for compiler that don't need this particular workaround but to generally let them return a positive result instead. Thus, I suggest to change partial_workaround in boost.range to behave this way. Stefan
Stefan Slapeta wrote:
I remember that we agreed not to fail workaround tests for compiler that don't need this particular workaround but to generally let them return a positive result instead.
Thus, I suggest to change partial_workaround in boost.range to behave this way.
What particular code change do you suggest? -Thorsten
Thorsten Ottosen wrote:
What particular code change do you suggest?
see attachment. stefan diff -u -r1.9 partial_workaround.cpp --- partial_workaround.cpp 18 Apr 2005 09:05:44 -0000 1.9 +++ partial_workaround.cpp 17 Dec 2005 14:21:36 -0000 @@ -105,14 +105,10 @@ #else // BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION -#include <boost/test/unit_test.hpp> -using boost::unit_test::test_suite; - -test_suite* init_unit_test_suite( int, char** ) +int main() { - test_suite* test = BOOST_TEST_SUITE( "Range Test Suite" ); - - return test; + // always succeed + return 0; } #endif
participants (2)
-
Stefan Slapeta -
Thorsten Ottosen