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

multiple definition error when linking with filesystem
by frederic.bron＠alcan.com 30 Jun '07

30 Jun '07

I have 2 .cpp files which both includes : #include <boost/filesystem.hpp> #include <boost/regex.hpp> When I link the 2 .o with -lboost_filesystem -lboost_regex, I get the following error message: obj_o/BBron/TraceFileExtraction.o:TraceFileExtraction.cc:(.text+0x3d0): d'efinitions multiples de << boost::filesystem::basename(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&)>> obj_o/BBron/AverageEvenCurve.o:AverageEvenCurve.cc:(.text+0x0): d'efini pour la premi`ere fois ici obj_o/BBron/TraceFileExtraction.o:TraceFileExtraction.cc:(.text+0x4d0): d'efinitions multiples de << boost::filesystem::extension(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&)>> obj_o/BBron/AverageEvenCurve.o:AverageEvenCurve.cc:(.text+0x170): d'efini pour la premi`ere fois ici collect2: ld a retourn'e 1 code d''etat d'ex'ecution What's the problem? F. Bron ___________________________________ Frédéric Bron (frederic.bron(a)alcan.com) Unité ALT, Alcan CRV, BP 27, 38341 Voreppe téléphone : +33 4 76 57 81 72 télécopie : +33 4 76 57 80 99 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.

1 2

2 x Boost.Log
by Andrej van der Zee 30 Jun '07

30 Jun '07

Hi, I am looking for a Logging library in C++ and found two Boost libraries: * one by Andrey Semashev (with an empty sourceforge project created recently). * one by John Torjo (outdated downloadable from his website). Is any of those two already reviewed/accepted by Boost? Thanks, Andrej ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/

1 0

troubles linking with boost_regex
by frederic.bron＠alcan.com 29 Jun '07

29 Jun '07

I am using boost 1.34.0 I have built the boost libraries from cygwin but for no-cygwin environment (pure win32, independant from cygwin): - I have built bjam with: ./build.bat gcc-nocygwin - I have used bjam like this: path/to/bjam link=static threading=single runtime-link=shared --toolset=gcc-nocygwin --prefix="D:\Softs\boost_msw" --layout=system release install - I then use g++ with -mno-cygwin flag to compile and link Here is the trouble I get when I link a program that uses regex with the regex library: /cygdrive/d/Softs/boost_msw/lib/libboost_regex.a(static_mutex.o):static_mutex.cpp:(.text+0x1a): r'ef'erence ind'efinie vers << _pthread_mutex_lock >> /cygdrive/d/Softs/boost_msw/lib/libboost_regex.a(static_mutex.o):static_mutex.cpp:(.text+0x54): r'ef'erence ind'efinie vers << _pthread_mutex_lock >> /cygdrive/d/Softs/boost_msw/lib/libboost_regex.a(static_mutex.o):static_mutex.cpp:(.text+0x84): r'ef'erence ind'efinie vers << _pthread_mutex_lock >> /cygdrive/d/Softs/boost_msw/lib/libboost_regex.a(static_mutex.o):static_mutex.cpp:(.text+0xaa): r'ef'erence ind'efinie vers << _pthread_mutex_unlock >> /cygdrive/d/Softs/boost_msw/lib/libboost_regex.a(static_mutex.o):static_mutex.cpp:(.text+0xda): r'ef'erence ind'efinie vers << _pthread_mutex_unlock >> /cygdrive/d/Softs/boost_msw/lib/libboost_regex.a(static_mutex.o):static_mutex.cpp:(.text+0x10a): r'ef'erence ind'efinie vers << _pthread_mutex_unlock >> This does not happen when I link a program that uses only filesystem with the filesystem library. Also when I use boost libraries built for cygwin environnement (configure;make install), I have no problem linking with regex. I have tried with threading=multi but obtained the same results. Maybe I should build the no-cygwin libraries totally outside cygwin, i.e. with a standalone compiler? Any tricks? 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 2

[Boost.MathToolKit] Compilation problem w/ VC++7.1
by Marc Viala 29 Jun '07

29 Jun '07

Hello, I've just tried to compile the following small code snippet: #include <boost/math/distributions/gamma.hpp> void main() { } But the compilation failed w/ the following errors: :\boost\math\special_functions\log1p.hpp(195) : error C2785: 'tools::promote_args<T>::type boost::math::log1p(T)' et 'double boost::math::log1p(double)' ont des types de retour différents \boost\math\special_functions\math_fwd.hpp(246) : voir la déclaration de 'boost::math::log1p' \boost\math\special_functions\log1p.hpp(182) : voir la déclaration de 'boost::math::log1p' \boost\math\special_functions\log1p.hpp(195) : error C2912: spécialisation explicite ; 'double boost::math::log1p<double>(double)' n'est pas une spécialisation d'un modèle de fonction C:\Dev\MViala\ADV\Library\boost-1_33_1\boost\math\special_functions\log1p.hpp(183) : fatal error C1903: impossible de récupérer à partir des erreurs précédentes ; arrêt de la compilation Compilation Conditions: - Windows XP Pro - Boost 1.33.1 w/ Math. Toolkit Headers files (extracted from Vault Directory) - Visual C++ 7.1 SP1 : Version 7.1.6030 Does anyone know how to manage Math.ToolKit headers file w/ Boost 1.33.1 and VC++ 7.1.6030 Best regards, Marc Viala

2 1

Re: [Boost-users] praise for multi_index
by "JOAQUIN LOPEZ MU?Z" 29 Jun '07

29 Jun '07

Hello Pedro, <boost <at> larroy.com> writes: > > 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) :) Thank you very much for your compliments! They're so rewarding, especially after a nightmarish work day :) Do not hesitate to contribute your proposals for improvement of the library. Best, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[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