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

Re: [Boost-users] [Boost.MathToolKit] Compilation problem w/ VC++7.1
by Marc Viala 30 Jun '07

30 Jun '07

Hello John, Yes, I've tried to compile w/ the right header version of math-toolkit. Just to be sure and to confirm the problem: Right now I'm using Boost 1.33.1. Do you confirm that math-toolkit can operate only w/ Boost 1.34? If yes, sorry for the noise. By the way, do you plan to adapt your headers for Boost 1.33.1? Marc Viala > -----Message d'origine----- > De : boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] De la part de John Maddock > Envoyé : samedi 30 juin 2007 10:34 > À : boost-users(a)lists.boost.org > Objet : Re: [Boost-users] [Boost.MathToolKit] Compilation problem w/ VC++7.1 > > Marc Viala wrote: > > Done but I've got the same compilation errors. > > Hmmm, works for me. BTW you will need Boost-1.34 to compile any of the > math-toolkit code. Other than that, are you sure you updated your #include > path to point to the sandbox version? Just double checking the obvious ;-) > > John. > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

[Boost.Graph] Visitors - dummy functions
by Ewgenij Sokolovski 30 Jun '07

30 Jun '07

Hello! I want to implement a visitor for the dijkstra_shortest_paths (...) algorithm. The visitor interface requires several methods which should be provided in each visitor object. But I need only one of these functions. So I considered to implement the others as empty functions like: void function(...) { } The problem now is, that as I apparently don't use the parameters, given to the function, inside of its body, the compiler prints out warnings about unused parameters. Is there a possibility to avoid this annoying thing? Except of disabling the warnings of the compiler in general. Regards Ewgenij -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

2 1

Re: [Boost-users] [Boost.MathToolKit] Compilation problem w/ VC++7.1
by Marc Viala 30 Jun '07

30 Jun '07

Done but I've got the same compilation errors. Sorry... Marc Viala > -----Message d'origine----- > De : boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] De la part de John Maddock > Envoyé : vendredi 29 juin 2007 20:13 > À : boost-users(a)lists.boost.org > Objet : Re: [Boost-users] [Boost.MathToolKit] Compilation problem w/ VC++7.1 > > Marc Viala wrote: > > Hello, > > > > I've just tried to compile the following small code snippet: > > > > #include <boost/math/distributions/gamma.hpp> > > void main() { } > > > Does anyone know how to manage Math.ToolKit headers file w/ Boost > > 1.33.1 and VC++ 7.1.6030 > > I think that's one I fixed recently: can you try the current sandbox source? > > Regards, John. > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

boost_regex with/without BOOST_REGEX_MATCH_EXTRA on same machine?
by Markus Grabner 30 Jun '07

30 Jun '07

Hi! For an application I'm writing, I need the match_results::captures feature, which requires to recompile boost with BOOST_REGEX_MATCH_EXTRA. I did so and globally installed the modified boost-1.33.1 on my machine. However, several utilities installed on my machine that came with my Linux distribution (openSUSE-10.2) don't work with the modified library (including the yast2 package manager, which made it somewhat challenging to re-install the original version). So I have two questions: *) What is the recommended installation if applications requiring BOOST_REGEX_MATCH_EXTRA must be installed on the same machine together with applications that don't require this extension? *) Are there any chances that future versions of the boost_regex library will remove this compile-time distinction? Are the few extra bytes for the (unused) m_captures member in sub_match really such a big problem? Thanks & kind regards, Markus -- Markus Grabner - Computer Graphics and Vision Graz University of Technology, Inffeldgasse 16a/II, 8010 Graz, Austria Phone: +43/316/873-5041, Fax: +43/316/873-5050 WWW: http://www.icg.tugraz.at/Members/grabner

2 1

[Test] Testing generated code.
by Michael Marcin 30 Jun '07

30 Jun '07

I have written type safe wrappers around some math operations that I need to use everywhere and I expect and rely on them being equivalent to the handcoded or macro based approach for performance reasons. I tend to check the resulting assembly by hand every so often and it surprises me from time to time to see that inefficiencies have crept in. If I write a routine in C and a routine using the type safe wrappers that I expect to have equivalent generated assembly is there a way to test that this is indeed the case? Can anyone else think of a better way to make sure that register usage is optimal, proper inlining is occurring, etc? Thanks, Michael Marcin

4 6

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

[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