May 2009 - Boost - lists.boost.org

Re: [boost] [test] Automatic registration of tests created with BOOST_PARAM_TEST_CASE
by Jan Stolarek 10 May '09

10 May '09

Ok, I figured out a solution that seems to be quite elegant, not so verbose and easy to achieve : using namespace boost::unit_test; class DataSet { public : DataSet( /* params */ ) { /* setup single data set */ } ~DataSet( ) { /* teardown single data set */ } /* some fields */ } void testMethod( DataSet* data ) { /* do something with method that's being tested. Use data somehow */ BOOST_CHECK( /* assertion */ ); } BOOST_AUTO_TEST_CASE( TestNameFirstDataSet ) { DataSet dataSet( /* params for first data set */ ); testMethod( dataSet ); } BOOST_AUTO_TEST_CASE( TestNameSecondDataSet ) { DataSet dataSet( /* params for second data set */ ); testMethod( dataSet ); } It's so simple that I wonder why didn't I figure it out right away. It doesn't require extra lines of code (dataSet has to be created somewhere anyway), it even allows to get rid of DataProvider class. Also there is no problem of spliting the tests into many files (I think this could be problematic if I had used global fixture, since all the data sets would have to be defined in one file). Any bad sides of this approach? Jan

1 0

[iostreams] regression - Missing include guard in boost/iostreams/device/mapped_file.hpp
by Bjørn Roald 10 May '09

10 May '09

Hi, Seems like the trunk@46692 commit, 25 june 2008, removed the include guard in boost/iostreams/device/mapped_file.hpp This breaks gcc43 compilation of sources directly including this header. Eg. http://www.mapnik.org/ trunk code. -- Bjørn

2 4

[Review Request] Boost.Convert
by Vladimir Batov 09 May '09

09 May '09

The proposed Boost.Convert has seen some lively discussions and considerable changes. Since then its interface and major implementation details have been unchanged and are being used/tested in an actual development of a system of a moderate size. Therefore, I would like to request a formal review and the component placed into the review queue. The zipped source and documentation are in the Vault: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost-… Thanks, Vladimir.

1 0

[utility][foreach][1.39.0] warning C4512
by Michael Mathews 08 May '09

08 May '09

HI folks, Just upgraded to 1.39.0 and everything works well except I started getting these warnings. >C:\Boost\include\boost-1_39\boost/utility/addressof.hpp(30) : warning C4512: 'boost::detail::addr_impl_ref<T>' : assignment operator could not be generated 1> with 1> [ 1> T=std::vector<double> 1> ] 1> C:\Boost\include\boost-1_39\boost/utility/addressof.hpp(56) : see reference to class template instantiation 'boost::detail::addr_impl_ref<T>' being compiled 1> with 1> [ 1> T=std::vector<double> 1> ] 1> C:\Boost\include\boost-1_39\boost/foreach.hpp(627) : see reference to function template instantiation 'T *boost::addressof<T>(T &)' being compiled 1> with 1> [ 1> T=std::vector<double> 1> ] 1> .\main.cpp(102) : see reference to function template instantiation 'boost::foreach_detail_::auto_any<T> boost::foreach_detail_::contain<std::vector<_Ty>>(std::vector<_Ty> &,boost::mpl::false_ *)' being compiled 1> with 1> [ 1> T=std::vector<double> *, 1> _Ty=double 1> ] msvc9 sp1 warning level 4. I didn't get these warnings in 1.38 enjoy michael

2 1

Does Boost has an utility to replace all OLD Keys with NEW one for MultiMap/Map?
by Tushar Chowdhury 08 May '09

08 May '09

Hi Guys, As of now I failed to get such an algo. I've come up with an proposed solution. Please verify: namespace Boost{ template <typename CONTAINER> void replace_key(CONTAINER& container, const typename CONTAINER::key_type& oldKey, const typename CONTAINER::key_type& newKey) { typename CONTAINER::iterator begin(container.find(oldKey)); for(;;){ if(begin != container.end()){ container.insert(typename CONTAINER::value_type(newKey, begin->second)); container.erase(begin++); begin = container.find(oldKey); } else{ return; } } } } make sense?

6 11

[test] Automatic registration of tests created with BOOST_PARAM_TEST_CASE
by JS 08 May '09

08 May '09

Hi, I want to create a test that a) runs the same testing function with different sets of input data AND b) registers automatically Obviously I can use BOOST_PARAM_TEST_CASE macro for a), but how do I achieve b) at the same time? I've been fighting with the problem for many hours and I have no idea how to do it. Unfortunately the documentation is very cryptic. Here's what I came up with so far: boost-main.cpp : #define BOOST_TEST_DYN_LINK #define BOOST_TEST_MAIN #define BOOST_TEST_MODULE My Master Test Suite #include <boost/test/unit_test.hpp> testSomeFunctions.cpp : using namespace boost::unit_test; class DataSet { public : DataSet( /* params */ ) { /* setup single data set */ } ~DataSet( ) { /* teardown single data set */ } /* some fields */ } class DataProvider { public : DataProvider() { dataSet.push_back( new DataSet( /* params */ ) ); /* add more if necessary */ } ~DataProvider() { /* free memory*/ } std::vector<DataSet*> dataSet; } void testMethod( DataSet* data ) { /* do something with method that's being tested. Use data somehow */ BOOST_CHECK( /* assertion */ ); } BOOST_AUTO_TEST_CASE( TestName ) { DataProvider dataProvider; test_suite* test = BOOST_TEST_SUITE( "I don't think the name matters" ); test->add( BOOST_PARAM_TEST_CASE( &testMethod, dataProvider.dataSet.begin(), dataProvider.dataSet.end() ) ); framework::run( test ); } However this is not correct since test cases created with BOOST_PARAM_TEST_CASE are not registered in the master test suite. If one of the tests fails I get the following log : Running 1 test case... ../test/functions/testSomeFunctions.cpp(67): error in "testMethod": check data->a == data->b failed [2 != 3] *** No errors detected I tried replacing "framework::run( test );" with "framework::master_test_suite().add( test );" but that doesn't work at all (log says that no errors were detected, while there should be one test that fails). I also tried something like this : BOOST_AUTO_TEST_CASE( ActivationFunctionTest ) { DataProvider dataProvider; framework::master_test_suite().add( BOOST_PARAM_TEST_CASE( &testMethod, dataProvider.dataSet.begin(), dataProvider.dataSet.end() ) ); } but the result is the same (No errors detected). What should I do? Jan

2 1

[spirit2] conflict with asio header
by Michael Caisse 07 May '09

07 May '09

I'm not certain if this is an asio issue or spirit2 issue (or user error). I checked Spirit out from the trunk and placed it into a 1.37 boost tree. I'm running gcc 4.3.2. Creating file foo.cpp with the following: --------------- #include <boost/asio.hpp> #include <boost/spirit/include/qi.hpp> --------------- Produces a string of errors including this snippet: from ../src/foo.cpp:3: ../../../library/vendor/boost/boost/proto/make_expr.hpp: At global scope: ../../../library/vendor/boost/boost/proto/make_expr.hpp:935: error: expected nested-name-specifier before numeric constant ../../../library/vendor/boost/boost/proto/make_expr.hpp:935: error: expected â>â before numeric constant ../../../library/vendor/boost/boost/proto/make_expr.hpp:940: error: type/value mismatch at argument 3 in template parameter list for âtemplate<class Tag, class DomainOrA0, class A0, class A1, class A2, class A3, class A4, class Void> struct boost::proto::result_of::make_exprâ ../../../library/vendor/boost/boost/proto/make_expr.hpp:940: error: expected a type, got â0â ../../../library/vendor/boost/boost/proto/make_expr.hpp:940: error: expected initializer before âconstâ Swapping the include order resolves the error. Should I enter a ticket? Michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

3 2

Submitting a patch to the bug/ticket list
by Juan Antonio Zaratiegui Vallecillo, a.k.a. Zara 07 May '09

07 May '09

Well, I have submitted a patch for dynamic_bitset.hpp, and I have seen that the ticket is now 'closed' and 'fixed'. I don know if it is an automatic response from the system, or if I have done something wrong (like, for instance, clicking where I should not click), and in such case I should reopen the ticket. Please, tell me which is the case and what should I do, because I am not happy leaving it this way. BTW, the bug owner is listed as gennaro_prota. Should I try to contact him directly? TIA Zara

2 3

gcc-4.4.0 and boost::optional is giving (spurious?) strict-aliasing warnings
by Brad Spencer 07 May '09

07 May '09

Before I get to the details, let me start by saying that I suspect that these warnings are probably spurious. But, before I go and start asking the compiler folks if they are bugs, I'd like to check here first. If you take unmodified boost-1.38.0 and try to use boost::optional with gcc-4.4.0 -Wall -O3, you seem to get warnings about strict-aliasing rules being broken. If boost::optional (and boost::function) are really broken, then we're probably in trouble :) test.cc: #include <boost/optional.hpp> boost::optional<int> x; int func() { return *x; } On x86_64-unknown-linux-gnu: $ /opt/gcc-4.4.0/bin/g++ -Wall -O3 -I. -c -o test.o test.cc test.cc: In function ‘int func()’: test.cc:5: warning: dereferencing pointer ‘<anonymous>’ does break strict-aliasing rules ./boost/optional/optional.hpp:594: note: initialized from here I have seen some similar issues with boost::bind and boost::function, but I haven't isolated them down to something this simple yet. I figured I'd start by asking about this. So, is it safe to presume that boost::optional is not really breaking the strict aliasing rules? (It's not immediately obvious.) If so, then I can ask the gcc folks about this. Thanks! -- ---------------------------------------------------------- Brad Spencer - spencer(a)starscale.com - www.starscale.com

4 3

[thread] on_tls_prepare in win32\tss_pe.cpp incompatible with static linkage to a /clr object
by Matthew Chambers 07 May '09

07 May '09

I'm very interested in being able to have a native C++ executable which makes use of boost's TSS and also be able to wrap .NET modules with C++/CLI (i.e. /clr). And I much prefer it to be statically linked. The C++/CLI wrappers work fine when they are dynamically linked, but they cause a runtime initialization error (0xc000007b) whenever they are connected in only static links. It doesn't matter whether the host executable is compiled with /clr or not - somehow the MSVC linker knows to add some CLR initialization voodoo to the PE header whenever a static link to a /clr-enabled object is made. And that PE header voodoo seems to be incompatible with some of boost::thread's own brand of PE header voodoo which appears to be intended to provide TLS support for Windows. But as far as I can tell, I was able to get TLS working with MSVC9 even after commenting out the on_tls_prepare lines in tss_pe.cpp - commenting out the other lines wasn't necessary: > #if (_MSC_VER >= 1400) > //#pragma section(".CRT$XIU",long,read) > #pragma section(".CRT$XCU",long,read) > #pragma section(".CRT$XTU",long,read) > #pragma section(".CRT$XLC",long,read) > static __declspec(allocate(".CRT$XLC")) _TLSCB > __xl_ca=on_tls_callback; > // static __declspec(allocate(".CRT$XIU"))_PVFV p_tls_prepare = > on_tls_prepare; > static __declspec(allocate(".CRT$XCU"))_PVFV p_process_init = > on_process_init; > static __declspec(allocate(".CRT$XTU"))_PVFV p_process_term = > on_process_term; > #else I put together a test case that I'm pretty sure shows that TLS still works without that function. At the very least, can there be some preprocessor define to manually disable it for CLR compatibility? Or perhaps there is a way to adjust this voodoo to be compatible with the CLR initialization? I'm hosting the test case at: http://fenchurch.mc.vanderbilt.edu/files/TLS_CLR_Test.7z It includes a main function which runs a test of the TSS semantics, and a CLR class which tests console output via C++/CLI. I included binaries and the boost_thread.lib files for both the broken and "fixed" versions of tss_pe.cpp. Thanks, Matt Chambers

2 2