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

[Test] Random seed
by Sohail Somani 29 Jun '07

29 Jun '07

Is there a way to get Boost.Test to spit out the seed it uses for randomizing the test case order? log_level=test_suite is too noisy. I basically want seed + normal output. Thanks, Sohail

2 2

[serialization] extended_type_info.cpp: assert(lookup(eti) == m_self->m_map.end());
by Markus Bernhardt 29 Jun '07

29 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, I'm using serialization for quite a while now. Everything worked for me. Now I added some classes to serialization and one off my classes causes an assertion. This happens with 1.32.0 and 1.34.0. I'm quite sure my code is broken, but I can't find it. Therefore I was debugging and it looks weird. 1. OS: Solaris 10 CC: Sun C++ 5.8 Patch 121018-10 2007/02/21 (latest patch level) Reproducable under Sparc and x86 2. The programm crashes on startup: (dbx) where current thread: t@1 [1] __lwp_kill(0x1, 0x6, 0xfffffe8200db3500, 0x3, 0xfffffd7fffdff2a0, 0xfffffd7fff3c73a0), at 0xfffffd7ffd7fe81a [2] _thr_kill(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffd7f9803 [3] raise(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffd7a7849 [4] abort(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffd78a7e0 [5] __assert(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffd78aa6e =>[6] boost::serialization::detail::tkmap::insert(eti = 0xfffffd7fff357540), line 78 in "extended_type_info.cpp" [7] boost::serialization::extended_type_info::self_register(this = 0xfffffd7fff357540), line 231 in "extended_type_info.cpp" [8] boost::serialization::detail::extended_type_info_typeid_1<const de::scmb::bm::core::SyncedRedoableWriteCommand<de::scmb::bm::core::Instance> >::extended_type_info_typeid_1(this = 0xfffffd7fff357540), line 77 in "extended_type_info_typeid.hpp" [9] boost::serialization::detail::extended_type_info_typeid_1<const de::scmb::bm::core::SyncedRedoableWriteCommand<de::scmb::bm::core::Instance> >::get_instance(), line 96 in "extended_type_info_typeid.hpp" [10] boost::archive::detail::pointer_oserializer<de::scmb::bm::core::SyncedRedoableWriteCommand<de::scmb::bm::core::Instance>,boost::archive::binary_oarchive>::pointer_oserializer(this = 0xfffffd7fff3576b8), line 234 in "oserializer.hpp" [11] __SLIP.INIT_E(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2db3bf [12] __STATIC_CONSTRUCTOR(), line 197 in "oserializer.hpp" [13] __cplus_fini_at_exit(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff320fd2 [14] call_init(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff3d278a [15] setup(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff3d1491 [16] _setup(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff3ded6f [17] _rt_boot(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff3c717f 3. The assertion is: assert(lookup(eti) == m_self->m_map.end()); (dbx) print -r lookup(eti) lookup(eti) = { _Rb_tree_iterator<const boost::serialization::extended_type_info*,std::_Const_traits<const boost::serialization::extended_type_info*> >::_Rb_tree_base_iterator::_M_node = (nil) } (dbx) print -r m_self->m_map.end() m_self->m_map.end() = { _Rb_tree_iterator<const boost::serialization::extended_type_info*,std::_Const_traits<const boost::serialization::extended_type_info*> >::_Rb_tree_base_iterator::_M_node = (nil) } Why the assertion is triggered ??? Both sides are "(nil)". 4. To get a better understanding I added a trace to extended_type_info.cpp: insert(const extended_type_info * eti){ if(NULL == m_self){ static tkmap instance; m_self = & instance; } // markus std::cout << eti->m_type_info_key << ": " << &(eti->m_type_info_key) << std::endl; // make sure that attempt at registration is done only once assert(lookup(eti) == m_self->m_map.end()); m_self->m_map.insert(eti); } The result confuses me even more: (dbx) run Running: bm_instd (process id 22999) extended_type_info_typeid: 0xfffffd7ffe5467b8 extended_type_info_typeid: 0xfffffd7ffe546808 extended_type_info_typeid: 0xfffffd7ffe546858 extended_type_info_typeid: 0xfffffd7ffe5468a8 extended_type_info_typeid: 0xfffffd7ffe5468f8 extended_type_info_typeid: 0xfffffd7ffe546948 extended_type_info_typeid: 0xfffffd7ffe546998 extended_type_info_typeid: 0xfffffd7ffe5469e8 extended_type_info_typeid: 0xfffffd7ffe546a38 extended_type_info_typeid: 0xfffffd7ffe546a88 extended_type_info_typeid: 0xfffffd7ffe546ad8 extended_type_info_typeid: 0xfffffd7ffe546b28 extended_type_info_typeid: 0xfffffd7ffe546b78 extended_type_info_typeid: 0xfffffd7ffe546bc8 extended_type_info_typeid: 0xfffffd7ffe546c18 extended_type_info_typeid: 0xfffffd7ffe546c68 extended_type_info_typeid: 0xfffffd7ffe546cb8 extended_type_info_typeid: 0xfffffd7ffe54b2d8 extended_type_info_typeid: 0xfffffd7ffe54b750 extended_type_info_typeid: 0xfffffd7ffe54bc58 extended_type_info_typeid: 0xfffffd7ffe54b700 extended_type_info_typeid: 0xfffffd7ffe54b970 extended_type_info_typeid: 0xfffffd7ffe54bac0 extended_type_info_typeid: 0xfffffd7ffe54c270 extended_type_info_typeid: 0xfffffd7ffe54bba8 extended_type_info_typeid: 0xfffffd7ffe54d4e8 extended_type_info_typeid: 0xfffffd7ffe54d180 extended_type_info_typeid: 0xfffffd7ffe54e5a8 extended_type_info_typeid: 0xfffffd7ffe54e5f8 extended_type_info_typeid: 0xfffffd7ffe54e648 extended_type_info_typeid: 0xfffffd7ffe550778 extended_type_info_typeid: 0xfffffd7ffe551870 extended_type_info_typeid: 0xfffffd7ffe5521d0 extended_type_info_typeid: 0xfffffd7ffe5529a8 extended_type_info_typeid: 0xfffffd7ffe553180 extended_type_info_typeid: 0xfffffd7ffe553958 extended_type_info_typeid: 0xfffffd7ffe554130 extended_type_info_typeid: 0xfffffd7ffe554908 extended_type_info_typeid: 0xfffffd7ffe5550e0 extended_type_info_typeid: 0xfffffd7ffe5558b8 extended_type_info_typeid: 0xfffffd7ffe556090 extended_type_info_typeid: 0xfffffd7ffe556868 extended_type_info_typeid: 0xfffffd7ffe5581f0 extended_type_info_typeid: 0xfffffd7ffe558670 extended_type_info_typeid: 0xfffffd7ffe558238 extended_type_info_typeid: 0xfffffd7ffe558a48 extended_type_info_typeid: 0xfffffd7ffe558ac0 extended_type_info_typeid: 0xfffffd7ffe559108 extended_type_info_typeid: 0xfffffd7fff357598 extended_type_info_typeid: 0xfffffd7fff357548 Assertion failed: lookup(eti) == m_self->m_map.end(), file libs/serialization/src/extended_type_info.cpp, line 78 t@1 (l@1) signal ABRT (Abbrechen) in __lwp_kill at 0xfffffd7ffd7fe81a 0xfffffd7ffd7fe81a: __lwp_kill+0x000a: jae __lwp_kill+0x18 [ 0xfffffd7ffd7fe828, .+0xe ] Current function is boost::serialization::detail::tkmap::insert 78 assert(lookup(eti) == m_self->m_map.end()); If I understand that right, it looks like extended_type_info_typeid: 0xfffffd7fff357548 is already in the map. How can that be? I think I'm completely missing the point at the moment. Can anyone suggest me where to look for the problem? Any comments are greatly appreciated. - markus - -- Software Consulting Markus Bernhardt GmbH Spieljochstr. 34 81825 München Fon: +49-89-420903-14 Fax: +49-89-420903-20 www: http://www.scmb.de Geschäftsführung Markus Bernhardt Handelsregister AG München HRB 125966 USt-Id DE201885231 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGhOtUdnooMonJSYkRAnhWAJ0cQPXyO7IZ2g6X5HNG55CzqFppBACfZDU6 3XpX5bmP0yqrFTrAyntWBIs= =0SAJ -----END PGP SIGNATURE-----

1 1

ASIO: Detecting broken connections
by Andrej van der Zee 29 Jun '07

29 Jun '07

Hi, I was wondering how I can find out with ASIO whether a connection is broken. I have a client connected to the server that continuously streams data. I have to know at the client-side when the server has hung up. I tried to use an async_write and after 5 erroneous tries the running thread for the connection is terminated. Like this: void connection::run_thread() { while (!stopped()) { event_ptr e = fetch_event(); if (!stopped()) { int write_tries = 0; boost::asio::async_write(_socket, boost::asio::buffer(*e, e->length()), boost::bind(&connection::handle_write, this, boost::asio::placeholders::error, e, write_tries)); } } } void connection::handle_write(const boost::system::error_code &err, const event_ptr event, int write_tries) { if (write_tries == max_write_tries) stopped(true); // thread will break out of its main-loop after being notified if (stopped()) return; // no meaning to continue if (err) { // incremenent write_tries and retry async_write boost::asio::async_write(_socket, boost::asio::buffer(*event, event->length()), boost::bind(&connection::handle_write, this, boost::asio::placeholders::error, event, ++write_tries)); } } I think I am misunderstanding something. I thought that after a async_write the registered handler will be invoked. But the handler is NEVER invoked somehow, although data is send from the client to the server. I have the following questions: - Why is the handler never invoked? When is it supposed to be invoked? - What is the best way to find out a connection has been reset by the server? And client? Thanks alot, Andrej ___________________________________________________________ Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your free account today http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.ht…

3 5

Boost.Serialization compile errors using the XLC compiler.
by Joe 29 Jun '07

29 Jun '07

I am using XLC under Linux/PPC with boost 1.33.1 compiled with XLC 8.0. I get the following errors when I attempt to compile the demo_xml.cpp example to compile. xlc++ -o demo_xml-xlc demo_xml.cpp -qstaticlink -I/home/jdavidso/boost/boost_xlc/include/boost-1_33_1 -L/home/jdavidso/boost/boost_xlc/lib -lboost_serialization-xlc-mt -lpthread "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/archive/detail/oserializer.hpp", line 333.13: 1540-1109 (S) The use of undefined class "boost::STATIC_ASSERTION_FAILURE<0>" is not valid. "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/archive/detail/oserializer.hpp", line 331.50: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::save_pointer_type<boost::archive::xml_oarchive,bus_stop *>::abstract<bus_stop>::register_type(boost::archive::xml_oarchive &)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/archive/detail/oserializer.hpp", line 360.16: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::save_pointer_type<boost::archive::xml_oarchive,bus_stop *>::register_type<bus_stop>(boost::archive::xml_oarchive &, bus_stop &)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/archive/detail/oserializer.hpp", line 460.55: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::save_pointer_type<boost::archive::xml_oarchive,bus_stop *>::invoke(boost::archive::xml_oarchive &, bus_stop * const)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/archive/detail/oserializer.hpp", line 536.5: 1540-0700 (I) The previous message was produced while processing "boost::archive::save<boost::archive::xml_oarchive,bus_stop *>(xml_oarchive &, bus_stop * const &)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/archive/basic_xml_oarchive.hpp", line 91.10: 1540-0700 (I) The previous message was produced while processing "boost::archive::basic_xml_oarchive<boost::archive::xml_oarchive>::save_override<bus_stop * const>(const nvp<bus_stop * const> &, int)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/archive/detail/interface_oarchive.hpp", line 77.15: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::interface_oarchive<boost::archive::xml_oarchive>::operator<< <const boost::serialization::nvp<bus_stop * const> >(const nvp<bus_stop * const> &)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/serialization/collections_save_imp.hpp", line 43.12: 1540-0700 (I) The previous message was produced while processing "boost::serialization::stl::save_collection<boost::archive::xml_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(xml_oarchive &, const list<bus_stop *,std::allocator<bus_stop *> > &)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/serialization/list.hpp", line 44.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::save<boost::archive::xml_oarchive,bus_stop *,std::allocator<bus_stop *> >(xml_oarchive &, const list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/serialization/split_free.hpp", line 37.17: 1540-0700 (I) The previous message was produced while processing "boost::serialization::free_saver<boost::archive::xml_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >::invoke(boost::archive::xml_oarchive &, const std::list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/serialization/split_free.hpp", line 74.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::split_free<boost::archive::xml_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(xml_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/serialization/list.hpp", line 75.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::serialize<boost::archive::xml_oarchive,bus_stop *,std::allocator<bus_stop *> >(xml_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/serialization/serialization.hpp", line 125.13: 1540-0700 (I) The previous message was produced while processing "boost::serialization::serialize_adl<boost::archive::xml_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(xml_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/archive/detail/oserializer.hpp", line 148.5: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::oserializer<boost::archive::xml_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >::save_object_data(basic_oarchive &, const void *) const". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/archive/detail/oserializer.hpp", line 99.7: 1540-0700 (I) The previous message was produced while processing "class boost::archive::detail::oserializer<boost::archive::xml_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/serialization/access.hpp", line 109.10: 1540-0217 (S) "serialize" is not a member of "class list<bus_stop *,std::allocator<bus_stop *> >". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/serialization/access.hpp", line 104.17: 1540-0700 (I) The previous message was produced while processing "boost::serialization::access::serialize<boost::archive::xml_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(xml_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "/home/jdavidso/boost/boost_xlc/include/boost-1_33_1/boost/serialization/serialization.hpp", line 81.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::serialize<boost::archive::xml_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(xml_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". Thanks. -- Joe

1 0

praise for multi_index
by boost＠larroy.com 29 Jun '07

29 Jun '07

Hi I just wanted to praise boost::multi_index I think it's a great container. I'm starting to wonder now how I lived without it previously (with many individual maps and much complexity I guess) :) Regards. -- Pedro Larroy Tovar, pedro at larroy dot com | http://pedro.larroy.com/ * Las patentes de programación son nocivas para la innovación * http://proinnova.hispalinux.es/

1 0

[bind] using bind for << to ostream
by Mojmir Svoboda 29 Jun '07

29 Jun '07

Hello, i want to use bind to create a pair and forward it to an std::ostream, i.e. like: std::for_each(vec.begin(), vec.end(), bind(&write, std::cout, bind(constructor<std::pair<value_t, value_t> >(), _1, _1))); but the compiler says: ios_base.h:781: error: 'ios_base(const ios_base &)' is private boost/boost/lambda/detail/bind_functions.hpp:472: error: within this context boost/boost/lambda/detail/function_adaptors.hpp: In static member function `static void boost::lambda::function_adaptor< void (*)(ostream &, const pair<value_t, value_t> &) >::apply( void (*)(ostream &, const pair<value_t, value_t> &), const ostream &, const pair<value_t, value_t> &)' ... it seem that temporary is created? why? how to avoid it? i've tried the obvious way (at least for me): std::for_each(vec.begin(), vec.end(), (std::cout << bind(constructor<std::pair<value_t, value_t> >(), _1, _1))); but now the output from compiler is kind of 'heavy stuff' and i'm having difficulties to figure out what am i doing wrong. can you help me, please? many thanks for your attention, Mojmir --------8<---- complete source ------ #include <boost/lambda/bind.hpp> #include <boost/lambda/construct.hpp> #include <memory> #include <vector> #include <iostream> using namespace boost::lambda; typedef int value_t; typedef std::vector<value_t> vect_t; typedef std::vector<std::pair<value_t, value_t> > vect2_t; std::ostream & operator<< (std::ostream & os, std::pair<value_t, value_t> const & p) { return os; } void write (std::ostream & os, std::pair<value_t, value_t> const & p) { } int main () { vect_t vec; vect2_t vec2; vec.push_back(1); std::transform(vec.begin(), vec.end(), std::back_inserter(vec2), bind(constructor<std::pair<value_t, value_t> >(), _1, _1)); // ok /* std::for_each(vec.begin(), vec.end(), bind(&write, std::cout, bind(constructor<std::pair<value_t, value_t> >(), _1, _1)) ); std::for_each(vec.begin(), vec.end(), (std::cout << bind(constructor<std::pair<value_t, value_t> >(), _1, _1))); */ } This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

3 4

[multi-index] how to use in herit member as index
by hongleij＠126.com 29 Jun '07

29 Jun '07

//boost #include <boost/multi_index_container.hpp> #include <boost/multi_index/hashed_index.hpp> #include <boost/multi_index/member.hpp> using namespace ::boost; using namespace ::boost::multi_index; #include <string> struct Peer { std::string userid; }; struct CPeer:public Peer { int index; }; struct userid{}; typedef multi_index_container< CPeer, indexed_by< hashed_unique<tag<userid>,member<CPeer,std::string,&CPeer::userid> > > > CPeersType; //how could i use userid as an index in CPeer ,not in Peer, 一起来，150 万人同时在玩的梦幻西游

4 8

Re: [Boost-users] [multi-index] member ar guments [Was: how to use inheritmember as index]
by hongleij＠126.com 29 Jun '07

29 Jun '07

it my implemention, i use BOOST_TYPEOF instead of typeof(). it seems work well for gcc and vc7.1 , #include <boost/multi_index/member.hpp> //for member #include <boost/multi_index/mem_fun.hpp> //for const_mem_fun using boost::multi_index::member; using boost::multi_index::const_mem_fun; #include <boost/typeof/typeof.hpp> /* MEMBER */ template<typename T> struct get_details; template<typename Class, typename Member> struct get_details<Member Class::*> { typedef Class class_type; typedef Member member_type; }; #define MEMBER(MemPtr) \ member< \ get_details<BOOST_TYPEOF(MemPtr)>::class_type, \ get_details<BOOST_TYPEOF(MemPtr)>::member_type, \ MemPtr> /* CONST_MEM_FUN */ template<typename T> struct get_fun_details; template<typename Class, typename Type> struct get_fun_details<Type (Class::*)()const> { typedef Class class_type; typedef Type member_type; }; #define CONST_MEM_FUN(MemFunPtr) \ const_mem_fun< \ get_fun_details<BOOST_TYPEOF(MemFunPtr)>::class_type, \ get_fun_details<BOOST_TYPEOF(MemFunPtr)>::member_type, \ MemFunPtr>

1 0

Cross-compiling boost for win32 on linux
by rodolfo＠rodsoft.org 29 Jun '07

29 Jun '07

Hi, I used to be able to cross-compile boost on linux for win32 with boost.build v1 without problems, but now with v2 I cannot find the mingw toolset. It seems that now we can use gcc toolset but with a mingw flavor. So, where can I set this flavor? Everything I do makes bjam use plain g++ (for building to run on linux), not mingw32-g++ (run on win32). Regards, Rodolfo Lima.

4 8

Why can't I catch this exception in boost::thread?
by af001 29 Jun '07

29 Jun '07

#include <boost/thread/thread.hpp> #include <iostream> #include <exception> void helloworld() { std::cout << "Hello World!" << std::endl; throw(std::string("err")); } int main() { try { boost::thread thrd(&helloworld); thrd.join(); } catch(...) { std::cout<<"err"; } } -- View this message in context: http://www.nabble.com/Why-can%27t-I-catch-this-exception-in-boost%3A%3Athre… Sent from the Boost - Users mailing list archive at Nabble.com.

2 2

about shared_ptr
by Daniel Oberhoff 28 Jun '07

28 Jun '07

Hi all, I am using shared_ptr to ease implementation of a matlab file wrapper. Esepcially the fact that it is in tr1 and thus available on many platforms already pushed that decision. Now I was wondering about one thing: Is there a devent way, using shared_ptr, to hand out multiple references? What I mean is something like this: class Variable { shared_ptr<Variable> ref(); }; The problem with shared_ptr is, that, or so it seems, you can only create one directly from the object like this: shared_ptr<Variable> p(new Variable(...)); and all further references have to be created as copies of this (or copies of copies...). So I have to keep one of those around to make new ones. But I cannot keep one inside the class itself or else it will never be deleted (because it would reference itself). The same goes for weak_ptr, since there must be a live shared_ptr around for the object not to be deleted. The only way I can think of is implementing my own refcount and hooking into my own release method. THe problem with this is that I cannot, acoording to the docs, hook up the retain method, so each shared_ptr "cloud" (i.e. set of shared_ptrs that have been created from a common shared_ptr) is hooked up to one ref_count, so they might invalidate when the object stays alive, making any attached weak_ptrs useless. The other is using intrusive_ptr, but that a) is not in tr1 and b) does not have a weak ptr. I was also wondering why intrusive_ptr is not wrapped inside shared_ptr, i.e. why I cannot hook up both retain (increase refcount) and release into shared_ptr, but I suppose that is for the developers list. One other way I could think of would be that I keep a reference to the global ref_count of all the shared_ptrs, and creating new shared_ptrs on top of that, thus binding all shared_ptrs together, but that part does not seem to be exposed in the api. Any Ideas? Daniel Oberhoff ps: should it be possible to post to this list via gmane? I would like that much better, so this won't clog my inbox. But trying to post I keep getting error 441 in gnus

3 2

Re: [Boost-users] [serialization] problem with derived classes
by Johan Franzén 28 Jun '07

28 Jun '07

> Hello, > > I'm having an issue with serializing derived classes from a base class > pointer. I think I've narrowed it down to the simplest possible code. I > get an "unregistered class" exception at runtime even though I've > registered the derived class with BOOST_CLASS_EXPORT. Here's the code: > [ snip ] > ----------------------------------------------- > > X.hpp: > > #pragma once > > #include <boost/serialization/base_object.hpp> > #include "A.hpp" > > class X : public A > { > friend class boost::serialization::access; > template<class Archive> > void serialize(Archive & ar, const unsigned int) > { > ar & boost::serialization::base_object<A>(*this); > } > }; > > ------------------------------------------------ > > X.cpp: > > #include "X.hpp" > > #include <boost/serialization/export.hpp> > > BOOST_CLASS_EXPORT(X) > > ----------------------------------------------- > > As you can see, I don't have BOOST_CLASS_EXPORT in the X.hpp header. > This is the way I originally had it but then I got multiple definition > link errors when more than one class derived from A. The suggestion in > the serialization docs was to move the macro to a .cpp file. [ snip ] Hello Avery, I suspect You need to BOOST_CLASS_EXPORT(A) as well, since You do try to serialize an A in X's serialize() method. This is was I ended up doing when serializing a hierarchy of derived classes and a base class. I'm not sure how to do that in Your case, since I had all classes and all BOOST_CLASS_EXPORT macros in a single header file. HTH, Johan Franzén

4 4

Re: [Boost-users] [multi-index /mpl] fata l compile error when using a tag in VS7.1 with SP1
by hongleij＠126.com 28 Jun '07

28 Jun '07

when i clean the solution and then rebuild it,it is useless; >* Try disabling the option /Gm (Enable Minimal Rebuild.) Yes,i just turn off it,then the error disappear. ps: its really a painful thing waiting for compiling, it about 10s for that litte file in a pentium 2.8G cpu. 一起来，150 万人同时在玩的梦幻西游

2 1

Creating a property map inside Dijkstra Visitor
by Jonas Gabriel 28 Jun '07

28 Jun '07

Good afternoon, Inside a dijkstra visitor I would like to change the edge weights at some point, so in my visitor I'm trying to make a property map called weight : > template<class DynamicMap> > class gds_visitor : public dijkstra_visitor<> > { > public: > > gds_visitor(DynamicMap input):dynamic(input){} > > .... > > template <class Edge, class Graph> > void examine_edge (Edge e, Graph& g) { > typename property_map<Graph, edge_weight_t>::type weight; > weight=get(edge_weight, g); > > std::cout << "An edge is being examined..." << "\n"; > } > > protected: > DynamicMap dynamic; > }; where Graph: > typedef adjacency_list<listS, vecS, directedS, no_property, property<edge_weight_t, int> > Graph; and Edge: > typedef std::pair<int, int> Edge; But it is not compiling, mentioning a problem with weight 'soperator = . Thank you in advance, Jonas Gabriel

2 1

grapg problem: getting all vertices between source and sink
by gast128 28 Jun '07

28 Jun '07

Dear all, we have a simple problem: we want to know all vertices between a source and sink vertex in adirected graph. So my thoughts were to see if a vertex is reachable from both source and sink (by doing a breadth_first_search on the graph from source and a breadth_first_search from the sink on the reverse graph) and if reachable they lay in between. However this counts too much vertices. Consider graph So -> Si -> C. C is reachable from both So as reachable from Si using in edges. This is not good. The breadth_first_search should not perform an out_edge discover from Si. Do I have to implement my own breadth_first_search_with_stop or are there alternatives? Wkr, me

2 3

[multi-index /mpl] fatal co mpile error when using a tag in VS7.1 wit h SP1
by hongleij＠126.com 28 Jun '07

28 Jun '07

//boost #include <boost/multi_index_container.hpp> #include <boost/multi_index/hashed_index.hpp> #include <boost/multi_index/member.hpp> #include "boost/multi_index/key_extractors.hpp" using namespace ::boost; using namespace ::boost::multi_index; #include <string> struct Peer { std::string userid; int age()const {return age_;} private: int age_; }; struct CPeer:public Peer { int index; }; struct Peer_age_extractor { typedef int result_type; const int operator()(const CPeer& peer)const { return peer.age(); } }; struct userid{}; struct age{}; typedef multi_index_container< CPeer, indexed_by< hashed_unique<tag<userid>,member<Peer,std::string,&Peer::userid> >, hashed_non_unique<tag<age>,const_mem_fun<Peer,int,&Peer::age> >// // hashed_non_unique<const_mem_fun<Peer,int,&Peer::age> > //without a tag will be ok. //hashed_non_unique<tag<age>,Peer_age_extractor > //this line with cause the same question. > > CPeersType; I get this in vs7.1 with sp1: ------ Build started: Project: multi_index1, Configuration: Debug Win32 ------ Compiling... hash_test.cpp f:\boost_1_34_0\boost\mpl\aux_\preprocessed\plain\apply_wrap.hpp(48) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'f:\vs70builds\6030\vc\Compiler\CxxFE\sl\P1\C\main.c', line 1164) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information Build log was saved at "file://g:\cpp\boost\multi_index1\Debug\BuildLog.htm" multi_index1 - 1 error(s), 0 warning(s) yet this can compile well in gcc 3.4. i really don't know why. many thanks for JOAQUIN LOPEZ MU?Z 's past help.;-) 百万玩家同玩的乐园，人气爆发的梦幻西游

2 1

Passing variable no. of arguments in macro
by Prasanta K Chakravarty 28 Jun '07

28 Jun '07

Hi, I have a requirement of passing variable no. of arguments in macro. So, I have build Boost wave library and got .dll and .lib file. But I am not able to use it. Please help me out how to use that one. Thanks & Regards, Prasanta

1 0

Re: [Boost-users] [serialisation]Portable Binary Archives
by Pfligersdorffer, Christian 27 Jun '07

27 Jun '07

boost-users-bounces(a)lists.boost.org wrote: >> If you're talking about portable binary archives for >> Boost.Serialization, there's been talk, but I'm not sure what >> the status is - anyone have an implementation? I'd be willing >> to help / work with someone on it. >> > > That's what I am looking for. We need to get the file sizes down. We > could use text (XML is great for debugging but too big for final > release), but again that has its overheads. We generally don't use > floating point so that may help us. The link I posted does have a > portable implementation which I think uses IEEE754. I just wondered if > there was an official boost:serilisation version; obviously not!! Hello James, there _is_ a portable binary archive provided with the examples but as Robert Ramey points out in the code documentation, it is not complete as it lacks the floating point conversion. But if Johan is willing to fill this gap I am perfectly confident that we could have a comprehensive implementation in a few weeks. That is, if the issue that Dan Leibovich found in the example can be resolved. I follow the portable archive discussion with great interest since I would very much like to use it too. PS @ Cliff: Very interesting post! Do you know about when and if the endian library will enter the official boost release? I would find that useful too. Regards, -- Christian Pfligersdorffer Software Engineering EOS GmbH

6 8

[Serialization] portable binary archive
by Dan Leibovich 27 Jun '07

27 Jun '07

Hi, Few month ago I have started a thread about an issue with the potable binary archive demo: http://lists.boost.org/boost-users/2007/03/26274.php Robert, Were you able to find the exact bug? Thanks in advance Dan

2 2

[serialization] problem with derived classes
by Avery Fay 27 Jun '07

27 Jun '07

Hello, I'm having an issue with serializing derived classes from a base class pointer. I think I've narrowed it down to the simplest possible code. I get an "unregistered class" exception at runtime even though I've registered the derived class with BOOST_CLASS_EXPORT. Here's the code: ---------------------------------------------- main.cpp: #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <sstream> #include "A.hpp" #include "X.hpp" int main() { std::stringstream ss; const A * const test = new X; { boost::archive::text_oarchive oa(ss); oa << test; } A *test2; { boost::archive::text_iarchive ia(ss); ia >> test2; } return 0; } ----------------------------------------------- A.hpp: #pragma once #include <boost/serialization/access.hpp> class A { private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int) { ar & test; } int test; public: A() : test(0) {} virtual ~A() {} }; ----------------------------------------------- X.hpp: #pragma once #include <boost/serialization/base_object.hpp> #include "A.hpp" class X : public A { friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int) { ar & boost::serialization::base_object<A>(*this); } }; ------------------------------------------------ X.cpp: #include "X.hpp" #include <boost/serialization/export.hpp> BOOST_CLASS_EXPORT(X) ----------------------------------------------- As you can see, I don't have BOOST_CLASS_EXPORT in the X.hpp header. This is the way I originally had it but then I got multiple definition link errors when more than one class derived from A. The suggestion in the serialization docs was to move the macro to a .cpp file. Full output when I run this: terminate called after throwing an instance of 'boost::archive::archive_exception' what(): unregistered class Aborted (core dumped) Any help would be appreciated greatly, Avery

1 0

Re: [Boost-users] problem... maybe boost could help
by Ovanes Markarian 27 Jun '07

27 Jun '07

My idea is based on fact that you (program developer or another developer) know what is going to be send. What you are trying to do is erasing the type to some base and that would not work. So you send event must handle derived type and put it correctly to variant. A possible solution would be: template<class EventType_> void sendEvent(EventType_ const& ev) { m_eventContainer = ev; //<- now compiler knows exactly the type of ev m_derivedHelper->dispatchEvent(&m_eventContainer); } Best Regards, Ovanes On Fri, June 22, 2007 21:41, Lukasz wrote: > > Thanks for the fast reply. Your solution looked very good for my problem, so i tried to apply it. >However, there seems to be a problem. At the point when i call dispatchEvent (as in the below >example) is when i have the actual event to be sent. But i still only have a pointer to the base >class and by assigning it to the container, it always gets interpreted as a base event, even when >in reality it's some derived type. > > I tried a couple of approaches. In the first one, my variant contains only the derived type (base class is Event, derived is EventTest) , i.e. > > typedef boost::variant<EventTest> event_container; > > .... > event_container m_eventContainer; > ... > > void sendEvent(Event * event) > { > // Call Helper to dispatch the event to correct type > m_eventContainer = *event; > m_derivedHelper->dispatchEvent(&m_eventContainer); > } > > This won't work. The compiler complains that none of the overloads for >boost::detail::variant::make_initializer_node::apply can convert parameter 2. If i add the base >event type to the variant list, i.e. > > typedef boost::variant<Event, EventTest> event_container; > > it will work, but it will always trigger the processEvent with the base > class type. I haven't found any information as to how boost::variant treats a case of a pointer to >a base class (in this case, i'm not even actually passing the pointer but an object since for >pointers it just doesn't seem to work). Should it be able to automatically convert the type ? If >not, then i guess i'm back to square one, since i still can't cast the event... unless i maybe >misunderstood something ? The code i tried is pretty much what you gave me, with some minor >modifications. > > Thanks in advance for any further assistance. > > Lukasz K. > > [...]

4 8

[filesystem] where is replace_extension
by frederic.bron＠alcan.com 27 Jun '07

27 Jun '07

In the documentation of filesystem (1.34.0), at this position: http://www.boost.org/libs/filesystem/doc/tr2_proposal.html#Header-filesyste… we can read : template <class Path> Path replace_extension(const Path & p, const typename Path::string_type & new_extension); However, in boost_1_34_0.tar.bz2, I cannot find replace_extension in any file. Where is it? Regards, F. Bron Avis : Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes en tout ou en partie. Notice: This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part.

2 3

[interprocess] Interprocess and Daniel James'es unordered containers
by Aaron W. LaFramboise 27 Jun '07

27 Jun '07

I'm trying to use Daniel James'es unordered containers, from the vault, with Interprocess: typedef ip::allocator<T, ip::managed_windows_shared_memory::segment_manager> T_allocator; typedef typedef boost::unordered_set<T, T_hash, std::equal_to<T>, T_allocator> T_set; I get this error: boost\unordered\detail\hash_table_impl.hpp(419) : error C2039: 'destroy' : is not a member of 'boost::interprocess::allocator<T,SegmentManager>' The method 'destroy' is missing in CVS, even though its still present in the documentation at <http://cloud.prohosting.com/newfunk/boost/libs/interprocess/doc/html/boost/…>. Is there some other general-purpose allocator that would work here? Why is this method missing?

2 1

Boost.Function and template function
by gast128 27 Jun '07

27 Jun '07

Dear all, I get a crash when I try to wrap a template function with Boost.Function. I use VStudio 2003 sp1. But maybe the used syntax is wrong: #include <boost/function.hpp> struct SomeClass { }; template <typename T> bool func_template(T* p) { return (p != NULL); } void example1() { bool (*pf) (SomeClass*) = &func_template<SomeClass>; boost::function<bool (SomeClass*)> fc1 = &func_template<SomeClass>; boost::function1<bool, SomeClass*> fc2 = &func_template<SomeClass>; boost::function<bool (SomeClass*)> fc3 = pf; fc1(NULL); //crashes fc2(NULL); //crashes also fc3(NULL); //ok } Wkr, me

2 2

Wave lib - MS compatibility issue?
by NeBlackCat 26 Jun '07

26 Jun '07

Firstly hi everybody - this is my first post, and I'm just finding my feet with Boost:Wave. I've built and am playing with the wave driver (wave.exe) on an existing open source project, but I get an "error: ill formed preprocessor directive: import" error with the at a line: #import <msado15.dll> \ rename("EOF","adoEOF") \ no_namespace I thought this might have been an MS compatibility thing, as importing COM type libraries is obviously Windows-specific (and afaik #import does something different in GCC), but I've tried recompiling with BOOST_WAVE_SUPPORT_MS_EXTENSIONS (and have tried lots of other things) and it doesn't make any difference. Google hasn't shown anything up either. Does anyone know if I can turn this error off somehow?

2 1