May 2009 - Boost-users - lists.preview.boost.org

[boost-users][signals2] thread-safe disconnection for intrusively ref-counted objects
by Igor R 13 May '09

13 May '09

Hello, Is there any trick or customization that would allow the subj? I mean the following situation: // pseudo-code! class intrusively_refcounted : //... { private: void listenToAsyncSubsystem() { // signals will come from another thread asyncSubsystem_.someEvent.connect(slot_type(&intrusively_refcounted::handler, this).track(???)); // can't use here shared_ptr/weak_ptr for tracking } }; I could store a connection object, so that it would be destroyed/disconnected in ~intrusively_refcounted(), but I guess it's not thread-safe, just like the approach with "trackable". So what would be the correct approach? Thanks!

2 2

How to reduce the size of a output DLL file?
by ipangth 13 May '09

13 May '09

I used to build a DLL file with VS2005 & boost-1_33, the project used boost::thread, asio, serialization, filesystem, datetime,system, link static, /MT, and the output DLL file size is about 1.7M. Now I port the project to VS2008 SP1 with boost-1_36, but the output file size increase to 2.9M! The VS2008 DLL project just default setting. I do not know whether this problem is boost-1_36 OR vs2008. Can some one give me some tips for how to reduce the DLL out put file size? -- Best regards, aster

2 1

[Boost.Test]
by Ruediger Berlich 13 May '09

13 May '09

Hi there, I am using Boost.Test to run Unit tests for my code (Boost 1.39). For each class, I have a number of tests (implemented through BOOST_AUTO_TEST_CASE or BOOST_AUTO_TEST_CASE_TEMPLATE, respectively), organized in test suites (arranged in BOOST_AUTO_TEST_SUITE blocks). Each BOOST_AUTO_TEST_SUITE with the associated AUTO_TESTs is a separate compilation unit, thus localted in its own file. I would now like to make sure that tests are run in a specific order. After all these are unit tests, and I want the most basic components to be tested first. Is there a way to do this with the AUTO-environment, or do I have to resort to manual registration of test suites and/or test cases ? I have tried changing the linking order, but to no avail. As always thanks for a great library collection and any help provided! Best Regards, Ruediger

4 6

[operators] Implicit instantiation.
by Robert Jones 13 May '09

13 May '09

I need to write a map class which distinguishes read from writing using the subscripting notation, so I wrapped the std::map, forwarded all the typdefs and methods, except for operator[], like this template < class Key, class T, template < typename Core > class Access > struct my_map { typedef std :: map< Key, T > core_type; typedef Access< core_type > proxy_type; typedef typename core_type :: key_type key_type; // ...lots of other stuff... proxy_type operator[]( const key_type & key ); }; where a typical 'Access' policy might be something like this. template < class T > struct proxy { typedef T map_type; typedef typename map_type :: key_type key_type; typedef typename map_type :: mapped_type mapped_type; proxy( map_type & core, const key_type & key ); proxy operator = ( const mapped_type & value ); operator mapped_type & ( ) const; }; Ok, all that broadly works, except expressions like my_map< string, string, proxy > m; if ( m[ "fred" ] == "bloggs" ).... won't compile even with a bool operator==(proxy, proxy), because the compiler can't figure out the implicit type conversions. What's needed is friend bool operator == ( proxy, const mapped_type & ); inside the proxy class, which does work. However I'd also like operator!=() to work in the same way, so I thought boost::operators, hence the declaration of proxy becomes template < class T > struct proxy : boost :: equality_comparable< proxy< T >, typename T :: mapped_type > { ... }; Which solves the problem. Now, the next twist is that I'd like to be able to compare my_map elements against any type which I can lexically convert to the mapped type, so an operator like friend template < class U > bool operator==( proxy, const U & ); but how do I express that to boost::equality_comparable, since the U type is generated by implicit instantiation, which applies to functions but not to classes? Thanks for reading. - Rob

1 0

Compile error when using breadth_first_search with these adjacency_list template parameters
by Julian 13 May '09

13 May '09

Hi, I get one compiler error when using breadth_first search with the adjacency list shown below. template < typename Vertex> class bfs_reachable_set_visitor : public default_bfs_visitor { public: bfs_reachable_set_visitor(set<Vertex>* bucket): m_set(bucket) { } template < typename Graph > void discover_vertex(Vertex u, const Graph & g) { m_set->insert(u); } set<Vertex>* m_set; }; typedef adjacency_list<setS, listS, undirectedS, RectGraphVertexData> RectAreaGraph; typedef graph_traits<RectAreaGraph>::vertex_descriptor VDescriptor; struct RectGraphVertexData {}; void some_func() { RectAreaGraph g; set<VDescriptor> reachableSet; bfs_reachable_set_visitor<VDescriptor> setvis(&reachableSet); breadth_first_search(g, *(vertices(g).first), visitor(setvis)); } The error: /Developer/boost_1_39_0/boost/property_map.hpp:351: error: no match for 'operator+' in '((const boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::undirectedS, RectGraphVertexData, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>*)this)->boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::undirectedS, RectGraphVertexData, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>::iter + boost::get [with PropertyMap = boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::undirectedS, RectGraphVertexData, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, Reference = const boost::detail::error_property_not_found&, K = void*](((const boost::put_get_helper<const boost::detail::error_property_not_found&, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::undirectedS, RectGraphVertexData, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t> >&)((const boost::put_get_helper<const boost::detail::error_property_not_found&, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::undirectedS, RectGraphVertexData, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t> >*)(&((const boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::undirectedS, RectGraphVertexData, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>*)this)->boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::undirectedS, RectGraphVertexData, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>::index))), ((void* const&)((void* const*)(& v))))' For now, since it compiles with vecS, I can change to that, but I would prefer to have setS for edge and listS for vertex.

2 2

serialization in 1.39: crash on program exit
by Filip Peters 13 May '09

13 May '09

Hi, I just compiled our program with boost 1.39, upgraded from 1.38. Now on exit I get a crash, (unhandled exception: stack overflow). If I look at the call stack, it's filled with Scene.dll!boost::serialization::void_cast_detail::void_caster_shortcut::~void_caster_shortcut() Line 88 C++ Scene.dll!boost::serialization::void_cast_detail::void_caster_shortcut::`scalar deleting destructor'() + 0xf bytes C++ Scene.dll!boost::serialization::void_cast_detail::void_caster::recursive_unregister() Line 207 + 0x28 bytes C++ Scene.dll!boost::serialization::void_cast_detail::void_caster_shortcut::~void_caster_shortcut() Line 88 C++ Scene.dll!boost::serialization::void_cast_detail::void_caster_shortcut::`scalar deleting destructor'() + 0xf bytes C++ Scene.dll!boost::serialization::void_cast_detail::void_caster::recursive_unregister() Line 207 + 0x28 bytes C++ Scene.dll!boost::serialization::void_cast_detail::void_caster_shortcut::~void_caster_shortcut() Line 88 C++ Scene.dll!boost::serialization::void_cast_detail::void_caster_shortcut::`scalar deleting destructor'() + 0xf bytes C++ compiler: ms visual c++ 2008 boost 1.39.0 I have a whole lot of classes that are registered with BOOST_CLASS_EXPORT, and saved through a shared_ptr to a base class. If I remove the exports, start and quit the application, I don't get a crash. It was working fine in 1.37 and 1.38. (from 1.33.1 on in fact) Has anybody seen this before or any ideas? thx, Filip Peters

3 2

Serialization / No Default Constructor / Messy
by Dan Eaton 13 May '09

13 May '09

Hi, My question is similar to past questions asked regarding what to do when a class to be deserialized does not have a default constructor. I'm wondering, though, if there is any better way to support both the BINARY and TEXT archive types, than doing this: class MyClass { public: MyClass(int myVar); MyClass( boost::archive::text_iarchive & ar ) { ar >> *this; } MyClass( boost::archive::binary_iarchive & ar ) { ar >> *this; } friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int /* fileVersion */ ) { ar & myVar; } private: int myVar; } Specifically, I'd rather not have to have a constructor for each type of archive! Thanks :) Danny

2 1

BOOST_AUTO_UNIT_TEST
by Ross Boylan 13 May '09

13 May '09

In Boost 1.34, the version just released with Debian Lenny, the release notes for Boost.Test say BOOST_AUTO_UNIT_TEST renamed to BOOST_AUTO_TEST_CASE. Old name still provided but deprecated As far as I can tell, the old name is not provided. Presumably I can provide my own definition to work around this. I am trying to make my code compatible with various releases of Boost (including older ones that use the old name), so I can't just replace all old names with the new one. Ross

2 3

boost unit tests and command line args
by Zachary Turner 13 May '09

13 May '09

I have some unit tests that all use BOOST_AUTO_TEST_CASE. Is there a way for me to hook into the main function before any of my test cases are run to perform initialization, involving the command line arguments that were passed to the executable? Currently there is no main function, it's defined inside the boost headers, and I don't see an obvious way of hooking into it.

2 1

CMake Problems with boost 1.39
by Tan, Tom (Shanghai) 13 May '09

13 May '09

I used CMake to build boost 1.39 and found at least two problems: - In the cmakelist.txt file the BOOST_VERSION_MINOR is 38, instead of 39 - The generated boost.test libs have an additional "-s" to the file names, ex. libboost_unit_test_framework-vc90-mt-1_39-s.lib, instead of libboost_unit_test_framework-vc90-mt-1_39.lib. This will cause a linking error while using boost.test. this does noto happen to the bjamed results. Another thing I noticed but am not sure is that signal2 is not included in the CMake support(no cmakelists.txt under signals). It seems the cmakelist.txt file is still that of 1.38.

3 2