- Boost - lists.boost.org

[signals2] Compile errors when using signals2
by Carlos Rafael Giani 11 May '09

11 May '09

Hi, I had some compiling errors when I wanted to try out signals2. In predestructible.hpp line 33 there is an extra semicolon (the empty {} scope has a an extra ;). Also, in tracked_objects_visitor.hpp line 85, the "trackable" parameter is unused, which causes a warning. The warning is not critical, but the error is. It basically forces one to either manually fix the predestructible.hpp header, or to stop using the -pedantic flag. My flags: -Wextra -Wall -std=c++98 -pedantic

2 1

Boost Asio in Windows
by Kenny Stone 10 May '09

10 May '09

I'm trying to use asio in linux and windows, and I have to use a very specific way of starting my IO Service to get it to work in windows xp: void start() { tcp::endpoint endpoint = *iterator_; socket_.async_connect(endpoint, boost::bind(&MessageHandler::handle_connect, this, boost::asio::placeholders::error, ++iterator_ ) ); boost::thread t( boost::bind( &boost::asio::io_service::run, &(socket_.get_io_service() ))); t.detach(); //threadPool_.schedule(boost::bind( &boost::asio::io_service::run, &(socket_.get_io_service()) ) ); } The commented out line is what I wanted to use (threadpool), as thread detach is far from an ideal situation. To work in windows, I have to call io_service.run() in this function and thread detach; it doesn't seem to work any other way. Everything pretty much works in linux. Is there a pattern that I should be using here for cross platform usage of the library? Any ideas why the threadpool solution doesn't work in windows? ( http://threadpool.sourceforge.net/) Thanks, -- Kenny Stone Connamara Systems, LLC

2 1

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

10 May '09

> Boost.Test do not support this setup out of the box It seems to me that there's no unit testing framework for C++ that would support that (please correct me if I'm wrong). > Which particular part? For example this : "Sub test case names are deduced from the macro argument test_case_name. If you prefer to assign different test case names, you need to use the underlying make_test_case interface instead." More details on that would be nice. It would also be great to add more complex examples. Examples for each section are clear, however problems arise when one tries to combine concepts from many sections. > This is not a good idea. I found it in documentation for Boost 1.34 : http://www.boost.org/doc/libs/1_34_1/libs/test/doc/tests/parameterized_test… > Your best shot probably is to try ot do this in global fixture. Would this be a good solution if I had many tests with lots of data sets? > You can implement your own generator. Could you point me to example on how to do that? >Also you probably should register your test units directly under >framework::master_test_suite() As mentioned in my fisrt mail I have tried that but with no result. It seems that I got something wrong with what I can add to master test suite. Jan

2 1

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 08 May '09

08 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