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

[boost] [interprocess] Semaphore cleanup after crash
by Sachin Garg 02 Aug '08

02 Aug '08

When using semaphores to synchronize separate processes, everything works fine when each process exits nicely (closing its semaphores before exit). But things get really messy when a process might crash. I am unable to figure out how to recover from such a crash which leaves semaphores in inconsistent state. If a semaphore is not in-use (open) by any process, in this case (in my application) I can safely 'remove' it and start afresh. Is there some way to find out if any process is using a semaphore at a time so that I can call 'remove'? When I just add a 'remove' on process start this works great on windows (as remove just fails if another process has the semaphore open), but on linux sem_unlink is used which has the behavior of deleting it even if its in use. What is the general practice when it comes to cleaning up semaphores after process crashes? Maybe some way to ensure that 'post' and 'close' are always called even when application has otherwise crashed? Is there some way to use boost's windows style semaphores on linux instead of native posix style? I tried looking and many have asked this question (in context of recovering from posix semaphores, which are used by boost on linux), but I couldn't find any answers. Lars had asked this here also, almost an year ago but no answers in that thread either. This seems like a basic issue but am totally lost on how to even approach it. Sachin Garg

4 11

Boost.Endian missing integer_cover_operators.hpp
by Seika van Olstroem 02 Aug '08

02 Aug '08

Hello, in 2000 and 2006 Darin Adler and Berman Dawes tried to get a library called Boost.Endian into Boost, but it seems the process stopped somewhere. This library would help me a lot when working with different byte orders. Here are the threads: http://lists.boost.org/Archives/boost/2000/03/2495.php http://lists.boost.org/Archives/boost/2006/06/106655.php Using Google I've found a recent endian.hpp but I can't find integer_cover_operators.hpp. http://lists.boost.org/Archives/boost/att-105789/endian.hpp Berman, what happend with Boost.Endian? -- -Seika

2 2

boost in NT Kernel
by Sam Tertzakian 02 Aug '08

02 Aug '08

Hi, Is it possible to use boost in the "NT Kernel" environment? It seems like I should be able to but I am only able to do so if I modify the library. I assume that there are two possibilities: 1. There is a #define that allows me to use in "NT Kernel". (Or there is some other step I need to do.) 2. boost is not supported (without modification) Thank you

2 2

Serial communications support
by Jean-Sebastien Stoezel 01 Aug '08

01 Aug '08

Hi, Is there a boost library available for serial communications (com port)? I could not find one based on the descriptions on the boost libraries page. Thanks, Jean

4 4

using wserialization library only
by Pramod Sharma 01 Aug '08

01 Aug '08

Hi , Can I use just wserialization( no serialization) library to achieve serialization ? I am using boost 1.32 and someone mentioned in MAC OS X platform , we have to use wseriliazation and seriliazation at link time , otherwise there will be undefined symbol error. I am planning to use only wserialization at link time. Please advise. Thanks, Pramod

2 2

Is there/ was there ever a compile-time rational in boost?
by John C. Femiani 01 Aug '08

01 Aug '08

Looking through the news-list I have found some discussion back in 2004 about a rational_c and a fixed_c class. http://lists.boost.org/Archives/boost/2004/06/66297.php Unfortunately the thread is broken up. The posters seem to use pairs of integers to represent rational numbers at compile time, apparently with specializations of MPL meta functions. Does anybody know what ever became of this? (I just spent all day writing something similar, but probably worse :) ) --John

2 1

[intrusive_ptr] Counting implementation
by Alexander Gutenev 01 Aug '08

01 Aug '08

Hello. I want to use intrusive_ptr as a smart pointer to have reference counting without shared_ptr overhead. There's no implementation for embedding reference counting into a pointee class provided by Boost.Smart Ptr library. I'd like to have reference counting easily embedded, like thru inheritance: class test : public intrusive_pointee_base<test> { ... }; I come to an implementation of this. As i'm sure this was coded many times before, two questions: (1) Why stock implementation of intrusive counter is not included to Smart Pointers library ? (2) Is there something wrong with my code ? struct refcount { refcount(void) : count_(0) {} refcount(refcount const&) : count_(0) {} refcount& operator=(refcount const&) {} long operator++(void) { return ::InterlockedIncrement(&count_); } long operator--(void) { return ::InterlockedDecrement(&count_); } private: mutable volatile long count_; }; template<class T> void intrusive_ptr_add_ref(T * p); template<class T> void intrusive_ptr_release(T * p); template<class Derived> class intrusive_pointee_base { friend void intrusive_ptr_add_ref<Derived>(Derived * p); friend void intrusive_ptr_release<Derived>(Derived * p); refcount reference_counter_; protected: ~intrusive_pointee_base(void) {} }; template<class T> void intrusive_ptr_add_ref(T * p) { intrusive_pointee_base<T> * pbase = p; ++(pbase->reference_counter_); } template<class T> void intrusive_ptr_release(T * p) { intrusive_pointee_base<T> * pbase = p; if (!--(pbase->reference_counter_)) delete p; }

7 24

Re: [Boost-users] [PATCH] boost_1.36 beta on AIX 5.3 with gcc 4.2.4: Compile errors in math
by Andrej van der Zee 01 Aug '08

01 Aug '08

Hi Watanabe-san, > Please submit a patch. There were more of these errors with identical solution. See attachment. Cheers, Andrej __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

2 1

Question on Serialization with derived classes
by Sergio (euitt-yegui-cho) 01 Aug '08

01 Aug '08

First of all, sorry for my written English. I would like to know if there is a way in XML Serialization to perform serialization of objects without class_id taking into account that the objects belong to classes that derive from a Base class. My desired xml files are something like: <call> <callrequest> <number>123456789</number> </callrequest> </call> <call> <callresponse> <state>connected</state> </callresponse> </call> So I have a class "Call" that contains a pointer to an object of a class "CallType". That class is abstract, and "CallRequest" and "CallResponse" implement some methods from it. When I try to serialize the classes , although I specify that want no class_id, object_id, etc., as I have to register the classes , then class_id is always added to xml syntax: <call class_id="1"> <callrequest class_id="2"> <number>123456789</number> </callrequest> </call> <call class_id="1"> <callresponse class_id="3"> <state>connected</state> </callresponse> </call> Is there a way to serialize objects deriving from other objects without serializing class_ids ? I guess there sould be a way to specify "tag callresponse" is for deserializing class "CallResponse" ... Thanks a lot. ¿No te gusta tu dirección de correo? Consigue una que te guste de verdad - millones de direcciones de correo disponibles en Yahoo! http://es.docs.yahoo.com/mail/nueva_direccion.html

1 0

Re: [Boost-users] [1.36.0 beta] Beta release available on SourceForge
by Lothar Werzinger 01 Aug '08

01 Aug '08

On Thursday 31 July 2008, Steven Watanabe wrote: > For wchar_t it might help to use wlocal_time_facet, e.g. > > In Christ, > Steven Watanabe I changed the code in the wide functions to use the wlocal_time_facet (see attached sample) and now both non wide and wide behave the same. Thanks for the hint! I still wonder why I can apply a local_time_facet. Intuition tells me it should either work or not compile. I never thought the facet could be wrong, as it compiled. Thanks again for pointing that out! Still the biggest problem remains and that is that the library produces an output that I can not read back. If you know what I am doing wrong here in the testInput* fuctions any help is appreciated! $ /opt2/linux/ix86/bin/g++-4.3.1 -I/opt2/linux/x86_64/include/boost-1_36 -o boost1 boost1.cpp && (./boost1; ./boost1 1; ./boost1 1 2; ./boost1 1 2 3) testing testInputIso ... expected=2005 actual =2005 expected=Sep actual =Sep expected=30 actual =30 expected=19 actual =19 expected=25 actual =25 expected=17 actual =17 expected=1 actual =0 boost1: boost1.cpp:100: void testInputIso(): Assertion `(true) == (0 != ldt.zone().get())' failed. testing testInputIsoWide ... expected=2005 actual =2005 expected=Sep actual =Sep expected=30 actual =30 expected=19 actual =19 expected=25 actual =25 expected=17 actual =17 expected=1 actual =0 boost1: boost1.cpp:150: void testInputIsoWide(): Assertion `(true) == (0 != ldt.zone().get())' failed. testing testOutputIso ... expected=2005-09-30 19:25:17+01:00 actual =2005-09-30 19:25:17+01:00 expected=2005-09-30 19:25:17-08:00 actual =2005-09-30 19:25:17-08:00 testing testOutputIso OK testing testOutputIsoWide ... expected=2005-09-30 19:25:17+01:00 actual =2005-09-30 19:25:17+01:00 expected=2005-09-30 19:25:17-08:00 actual =2005-09-30 19:25:17-08:00 testing testOutputIsoWide OK The biggest problem still is that the library produces an output that it can not read back. Both input Lothar -- Lothar Werzinger Dipl.-Ing. Univ. framework & platform architect Tradescape Inc. - Enabling Efficient Digital Marketplaces 1754 Technology Drive, Suite 128 San Jose, CA 95110 web: http://www.tradescape.biz

1 1

Re: [Boost-users] boost_3.6 beta: Linking boost serialisation (and other libs) gives duplicate symbol on AIX 5.3 with gcc 4.2.4
by Andrej van der Zee 01 Aug '08

01 Aug '08

Hi, > I don't like to force the compiler to behave in a way that is not > standard compliant. Or do you mean to force the compiler to > actually inline all inline functions? This is impossible for > virtual functions. Yes that is what I meant. Somehow the AIX linker does not inline a bunch of inline-functions resulting in these warnings. But I see now that this is not an option for virtual inline functions (but uhhhh, why would one inline a virtual function anyway? Seems like a contradiction). >> 2) Add the native AIX linker option: -bhalt:5 to suppress the warning > This is dangerous, since it may suppress real diagnostics, but at least > it is unlikely to break correct code. Yes I agree, this is what IBM sais: "The -bhalt link editor option specifies the maximum error level for the linking process to continue, and suppresses any error below the maximum." >> 3) Explicitely declare inline functions static > This can violate the ODR. It is out of the question as far as I am concerned. Hmmm, don't follow you here. > The linker ought not to be issuing a warning. I don't suppose there's a > way to make it shut up without also suppressing legitimate warnings, is > there? Not that I know of, but I have fairly limited experience on AIX. I just have to port a project... This is what IBM sais about possible solutions (it is for the AIX compiler xlCC, but the same native linker): "To have the V5.0 or V6.0 compiler give the non-inlined inline functions internal linkage, specify the-qstaticinlineflag when compiling your source files. Alternatively, the warning messages from ld can be suppressed by specifying the -bhalt:5flag when linking your application." Well, I guess there is no good solution then. Cheers, Andrej __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

1 0

boost_3.6 beta: Linking boost serialisation (and other libs) gives duplicate symbol on AIX 5.3 with gcc 4.2.4
by Andrej van der Zee 01 Aug '08

01 Aug '08

Hi, When (natively) linking on IBM AIX 5.3 after compiling with with gcc 4.2.4, I get the a bunch of link-warnings like below for many libraries. It seems that the reason is that inline function are linked externaly: http://www-1.ibm.com/support/docview.wss?uid=swg21044588 I am not sure what is the right way to solve the issue: 1) Force compiler to staticaly inline 2) Add the native AIX linker option: -bhalt:5 to suppress the warning 3) Explicitely declare inline functions static For now, the first seems best to me. But I dont think there is such an option. Or is there? Any other solutions? Cheers, Andrej gcc.link.dll bin.v2/libs/serialization/build/gcc-4.2.4/release/threading-multi/libboost_serialization-gcc42-mt-1_36.so ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::archive_exception::what() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::archive_exception::~archive_exception() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::archive_exception::~archive_exception() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::bad_alloc_impl::~bad_alloc_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::bad_alloc_impl::~bad_alloc_impl() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boosgcc.link.dll bin.v2/libs/serialization/build/gcc-4.2.4/release/threading-multi/libboost_serialization-gcc42-mt-1_36.so ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::archive_exception::what() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::archive_exception::~archive_exception() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::archive_exception::~archive_exception() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::bad_alloc_impl::~bad_alloc_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::bad_alloc_impl::~bad_alloc_impl() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::bad_alloc_impl::~bad_alloc_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::bad_alloc_impl::~bad_alloc_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::xml_archive_exception::what() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::xml_archive_exception::~xml_archive_exception() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::xml_archive_exception::~xml_archive_exception() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::xml_archive_exception::~xml_archive_exception() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::xml_archive_exception::~xml_archive_exception() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::xml_archive_exception::what() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::archive_exception::~archive_exception() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::archive_exception::~archive_exception() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::archive_exception::what() const ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. t::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::bad_alloc_impl::~bad_alloc_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::bad_alloc_impl::~bad_alloc_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::iterators::dataflow_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::xml_archive_exception::what() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::xml_archive_exception::~xml_archive_exception() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::archive::xml_archive_exception::~xml_archive_exception() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: .non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::xml_archive_exception::~xml_archive_exception() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::xml_archive_exception::~xml_archive_exception() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::xml_archive_exception::what() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::diagnostic_information() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::clone() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::add_ref() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::release() const ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: non-virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::rethrow() const ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::xml_archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::archive_exception::~archive_exception() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::archive_exception::~archive_exception() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::archive::archive_exception::what() const ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::error_info_injector<boost::archive::archive_exception>::~error_info_injector() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~exception_clone() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-224 WARNING: Duplicate symbol: virtual thunk to boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception> >::~clone_impl() ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

2 1

Re: [Boost-users] boost_1.36 beta on AIX 5.3 with gcc 4.2.4: Compile errors in math
by Andrej van der Zee 01 Aug '08

01 Aug '08

Hi, > Does it work with inline long double expm1l BOOST_PREVENT_MACRO_SUBSTITUTION(long double x) Yes it does. I found in total 4 instances of this error in the file ./boost/math/tr1.hpp. Shall I send a patch or are you doing it by hand? And uhhh, what triggered the error? I don't really get it.... Cheers, Andrej _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

2 1

boost_1.36 beta on AIX 5.3 with gcc 4.2.4: Compile errors in math
by Andrej van der Zee 01 Aug '08

01 Aug '08

Hi, Building on IBM AIX 5.3 with gcc 4.2.4 gives me the compile-time error below in math repeating itself endlessly. No such problems for boost_1.35. ...failed gcc.compile.c++ bin.v2/libs/math/build/gcc-4.2.4/release/threading-multi/cbrt.o... gcc.compile.c++ bin.v2/libs/math/build/gcc-4.2.4/release/threading-multi/copysign.o In file included from libs/math/build/../src/tr1/copysign.cpp:7: ./boost/math/tr1.hpp:438: error: 'boost::math::tr1::expm1' declared as an 'inline' variable ./boost/math/tr1.hpp:438: error: 'long double boost::math::tr1::expm1' redeclared as different kind of symbol ./boost/math/tr1.hpp:436: error: previous declaration of 'double boost::math::tr1::expm1(double)' ./boost/math/tr1.hpp:438: error: expected primary-expression before 'double' ./boost/math/tr1.hpp:438: error: expected `)' before 'double' ./boost/math/tr1.hpp:459: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:460: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:460: error: '::type' has not been declared ./boost/math/tr1.hpp:467: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:468: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:468: error: '::type' has not been declared ./boost/math/tr1.hpp:475: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:476: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:476: error: '::type' has not been declared ./boost/math/tr1.hpp:553: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:554: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:554: error: '::type' has not been declared ./boost/math/tr1.hpp:561: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:562: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:562: error: '::type' has not been declared ./boost/math/tr1.hpp:611: error: expected initializer before '<' token ./boost/math/tr1.hpp:612: error: expected initializer before '<' token It seems that the compiler sees the two following functions as the same symbols, although the name slight differs: inline double expm1(double x) { return boost::math::tr1::boost_expm1(x); } inline long double expm1l(long double x) { return boost::math::tr1::boost_expm1l(x); } Renaming the second function to __expm1l makes the error disappear. The same goes for the following functions: inline double log1p(double x) { return boost::math::tr1::boost_log1p(x); } inline long double log1pl(long double x) { return boost::math::tr1::boost_log1pl(x); } And the following: inline double nextafter(double x, double y) { return boost::math::tr1::boost_nextafter(x, y); } inline long double nextafterl(long double x, long double y) { return boost::math::tr1::boost_nextafterl(x, y); } Well, there is a clear pattern. After prefixing the second function with __ makes the errors go away. Could somebody enlighten me why this is? Greets, Andrej __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

2 1

[PATCH]: filesystem: Shadow Variables Cause Warnings/Errors When Headers Are Not in System Path
by Grant Erickson 01 Aug '08

01 Aug '08

In working through cross-compilation issues with boost, particularly the filesystem library, I discovered the following error reproduced with the following test case with both boost 1.34.1 and 1.35.0: FAILS: echo "#include <boost/filesystem.hpp>\nint main (void) { return (0); }" | g++ -o test -I/${BuildRoot}/results/boost/include -Werror -Wall -Wshadow -x c++ - PASSES: echo "#include <boost/filesystem.hpp>\nint main (void) { return (0); }" | g++ -o test -I/usr/include -Werror -Wall -Wshadow -x c++ - The failing case complains about 'what', 'path1' and 'path2' argument shadowing in boost/filesystem/path.hpp with respect to like-named member functions. Since GCC does not enforce warning options on headers in /usr/include, this only shows up when building against a boost installation outside /usr/include, as in the above failure example. The patch to address this is: Signed-off-by: Grant Erickson <gerickson(a)nuovations.com> --- --- boost_1_35_0/boost/filesystem/path.hpp 2008-07-30 16:54:53.000000000 -0700 +++ boost_1_35_0/boost/filesystem/path.hpp.N 2008-07-30 16:59:42.000000000 -0700 @@ -577,23 +577,23 @@ // BOOST_FILESYSTEM_DECL version works for VC++ but not GCC. Go figure! inline const char * what( const char * sys_err_what, - const path & path1, const path & path2, std::string & target ) + const path & path1_arg, const path & path2_arg, std::string & target ) { try { if ( target.empty() ) { target = sys_err_what; - if ( !path1.empty() ) + if ( !path1_arg.empty() ) { target += ": \""; - target += path1.file_string(); + target += path1_arg.file_string(); target += "\""; } - if ( !path2.empty() ) + if ( !path2_arg.empty() ) { target += ", \""; - target += path2.file_string(); + target += path2_arg.file_string(); target += "\""; } } @@ -607,7 +607,7 @@ template<class Path> const char * what( const char * sys_err_what, - const Path & /*path1*/, const Path & /*path2*/, std::string & /*target*/ ) + const Path & /*path1_arg*/, const Path & /*path2_arg*/, std::string & /*target*/ ) { return sys_err_what; } @@ -624,14 +624,14 @@ typedef Path path_type; - basic_filesystem_error( const std::string & what, + basic_filesystem_error( const std::string & what_arg, system::error_code ec ); - basic_filesystem_error( const std::string & what, - const path_type & path1, system::error_code ec ); + basic_filesystem_error( const std::string & what_arg, + const path_type & path1_arg, system::error_code ec ); - basic_filesystem_error( const std::string & what, const path_type & path1, - const path_type & path2, system::error_code ec ); + basic_filesystem_error( const std::string & what_arg, const path_type & path1_arg, + const path_type & path2_arg, system::error_code ec ); ~basic_filesystem_error() throw() {} @@ -1385,8 +1385,8 @@ template<class Path> basic_filesystem_error<Path>::basic_filesystem_error( - const std::string & what, system::error_code ec ) - : system::system_error(ec, what) + const std::string & what_arg, system::error_code ec ) + : system::system_error(ec, what_arg) { try { @@ -1397,29 +1397,29 @@ template<class Path> basic_filesystem_error<Path>::basic_filesystem_error( - const std::string & what, const path_type & path1, + const std::string & what_arg, const path_type & path1_arg, system::error_code ec ) - : system::system_error(ec, what) + : system::system_error(ec, what_arg) { try { m_imp_ptr.reset( new m_imp ); - m_imp_ptr->m_path1 = path1; + m_imp_ptr->m_path1 = path1_arg; } catch (...) { m_imp_ptr.reset(); } } template<class Path> basic_filesystem_error<Path>::basic_filesystem_error( - const std::string & what, const path_type & path1, - const path_type & path2, system::error_code ec ) - : system::system_error(ec, what) + const std::string & what_arg, const path_type & path1_arg, + const path_type & path2_arg, system::error_code ec ) + : system::system_error(ec, what_arg) { try { m_imp_ptr.reset( new m_imp ); - m_imp_ptr->m_path1 = path1; - m_imp_ptr->m_path2 = path2; + m_imp_ptr->m_path1 = path1_arg; + m_imp_ptr->m_path2 = path2_arg; } catch (...) { m_imp_ptr.reset(); } } ---

2 1

Re: [Boost-users] Boost spirit: overlapping inner struct result
by Kesseli Pascal 31 Jul '08

31 Jul '08

Hi Joel Thanks for your reply. That simple example you stated compiles fine, though. Is it possible that the templates might have ane impact here? "Joel de Guzman" <joel(a)boost-consulting.com> schrieb im Newsbeitrag news:<g6pu9q$r4b$1(a)ger.gmane.org>... > Pascal Kesseli wrote: > > Hi everyone > > > > When trying to compile the serialization library for my Montavista embedded > > computer, I am getting a strange error message concerning boost > > spirit/core/primitives/numerics.hpp stating that struct result in > > sign_parser has already been defined before. > > > > Back then, I couldn't deny that fact, as result is already defined in > > sign_parser's superclass parser, so I renamed the struct in the subclass to > > tresult and the library compiled fine. > > > > Currently, I am asking myself what influence such a change might have on > > the > > running program. I am having unexplainable SIGABRT signals appearing and > > killing my program, thus I suspect my change was not that mere after all. > > > > Is there a better workaround I could use to solve this problem? > > > > Thanks in advance for your replies and best regards > > I don't quite understand what's happening here. It shouldn't be > an error if a base class and a subclass share the same result > struct. Try this short example: > > struct x > { > struct result { typedef int type; }; > }; > > struct y : x > { > struct result { typedef double type; }; > }; > > Regards, > -- > Joel de Guzman > http://www.boostpro.com > http://spirit.sf.net

1 0

is BOOST_STATIC_WARNING part of boost public interface?
by frederic.bron＠alcan.com 31 Jul '08

31 Jul '08

I cannot find any documentation about BOOST_STATIC_WARNING, is it intended to be used by users or only internal to the library? 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.

3 3

[boost.thread] destruction of condition variables
by Vladimir Pozdyaev 31 Jul '08

31 Jul '08

Hello. Is it feasible to make CVs' destructors thread-safe? Consider the code below. It causes a failed assertion in basic_condition_variable::dispose_entry(...) when cv's destructor kicks in while notify_all() is still cleaning up. The problem is easily resolved by adding another mutex, but it would just look nicer if we could rely on cv's own features for that. Another alternative would be to make wait() return only after notify_xxx() has really finished its job. (Yes, I guess this code is not exactly a Good Practice :) , but it's not exactly logically inconsistent either. Or is it?) [ Boost 1.35.0, MSVC2008, Win32 Debug configuration Actually, it's not easy to make this particular code fail; adding a short sleep() in the beginning of dispose_entry(...) helps. This problem managed to appear quite systematically in a more complex program though. ] ---- Vladimir :::CODE::: #include <boost/thread.hpp> #include <boost/bind.hpp> class C { private: boost::mutex m; boost::condition_variable cv; public: ~C() { boost::mutex::scoped_lock l( m ); cv.wait( l ); } void fn() { boost::this_thread::sleep( boost::posix_time::milliseconds( 500 ) ); cv.notify_all(); } }; int main() { C c; boost::thread t( boost::bind( &C::fn, &c ) ); return 0; }

5 8

Boost with gcc 3.4.3?
by Karthick Gururaj 31 Jul '08

31 Jul '08

Hello, I am porting code which compiles with gcc 3.2.3 and uses boost, to compile for gcc 3.4.3. I get the following compilation errors. Also there are a lot of erros regarding scope, which can be fixed. Can anybody suggest what I should be looking at to resolve this. Regards Karthick /inc/boost/integer_fwd.hpp:70: error: `long_long_type' is not a member of `boost' /inc/boost/integer_fwd.hpp:70: error: `long_long_type' is not a member of `boost' /inc/boost/integer_fwd.hpp:70: error: template argument 1 is invalid /inc/boost/integer_fwd.hpp:73: error: `ulong_long_type' is not a member of `boost' /inc/boost/integer_fwd.hpp:73: error: `ulong_long_type' is not a member of `boost' /inc/boost/integer_fwd.hpp:73: error: template argument 1 is invalid /inc/boost/integer.hpp:20, inc/word_includes.hpp:34, /inc/word.hpp:34, /inc/boost/integer_traits.hpp:162: error: `long_long_type' is not a member of `boost' /boost/integer_traits.hpp:162: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:163: error: template argument 1 is invalid /boost/integer_traits.hpp:163: error: explicit specialization of non-template `<type error>' /inc/boost/integer_traits.hpp:163: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:163: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:163: error: template argument 1 is invalid /inc/boost/integer_traits.hpp:164: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:164: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:165: error: template argument 1 is invalid /inc/boost/integer_traits.hpp:165: error: `<type error>' is not a valid type for a template constant parameter /inc/boost/integer_traits.hpp:165: error: `<type error>' is not a valid type for a template constant parameter /inc/boost/integer_traits.hpp:168: error: `ulong_long_type' is not a member of `boost' //inc/boost/integer_traits.hpp:168: error: `ulong_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:169: error: template argument 1 is invalid /inc/boost/integer_traits.hpp:169: error: explicit specialization of non-template `<type error>'

2 2

boost program options future plans
by Aljaz 31 Jul '08

31 Jul '08

Hello Having an option to save-back configuration files would be a great feature of program option library. I've been wondering if there are any future plans for this? Also I have came across website http://code.google.com/p/clipo/ where idea for Clipo : Command Line Interpreter library based on the boost Program Option library is mentioned. This would be very useful as well. What do you think? Thanks for responses! Aljaz

2 1

about shared_ptr and object_pool
by Ken zhang 31 Jul '08

31 Jul '08

Hi dear all. I have a class named "session" look like below code: class session : public boost::enable_shared_from_this< session >, private boost::noncopyable { public: session(boost::asio::io_service& io_service); ..... }; I want use boost::object_pool for allocate memory for session. class host { public: typedef boost::object_pool<session> session_pool; host() : new_session_( session_pool_.construct(), boost::bind(&session_pool::destroy, &session_pool_)) { } public: boost::shared_ptr< session > new_session_; session_pool session_pool_; }; but there has a compiler error was occured: 1> d:\development\boost_1_35_0\boost\bind.hpp(1613) : warning C4180: qualifier applied to function type has no meaning; ignored 1> d:\development\boost_1_35_0\boost\bind.hpp(1647) : see reference to class template instantiation 'boost::_bi::add_cref<Pm,I>' being compiled 1> with 1> [ 1> Pm=void (__thiscall boost::object_pool<session>::* )(session *), 1> I=1 1> ] 1> d:\development\coreframework\portal\src\portal_server.cpp(16) : see reference to class template instantiation 'boost::_bi::dm_result<Pm,A1>' being compiled 1> with 1> [ 1> Pm=void (__thiscall boost::object_pool<session>::* )(session *), 1> A1=portal_server::session_pool *__w64 1> ] 1>d:\development\boost_1_35_0\boost\mem_fn.hpp(318) : warning C4180: qualifier applied to function type has no meaning; ignored 1> d:\development\boost_1_35_0\boost\bind\bind_template.hpp(344) : see reference to class template instantiation 'boost::_mfi::dm<R,T>' being compiled 1> with 1> [ 1> R=void (session *), 1> T=boost::object_pool<session> 1> ] 1>Project : error PRJ0002 : Error result 1 returned from 'C:\Program Files\Microsoft Visual Studio 8\VC\bin\cl.exe'. I use Microsoft visual studio 8 (vs2005). Thanks all Best regards. Yours Kenneth.Sh

2 2

boost::function, using undefined class?
by Erzengel Des Lichtes 31 Jul '08

31 Jul '08

Hello, I'm having an issue with boost::function in Visual Studio.NET 2005. In the following program: #include <boost/function.hpp> void SomeFunc(int* Blah) { //DoSomething } int __cdecl main(int argc, char* argv[], char* envp[]) { boost::function<void(*)(int*)> MyFunc; } I get the following error message: (Project Directory)\boostfunctest.cpp(11) : error C2079: 'MyFunc' uses undefined class 'boost::function' with [ Signature=void (__stdcall *)(int *) ] If I leave off the "(*)" it will compile, but this is just a simplified version of my real problem. The main reason this is a concern is I have a templated function that looks like this: template<typename Signature> boost::function<Signature> GetFunction(Signature ToCall); Which I intend to use to record and "play back" certain function calls. However, when it sees the signiture from the function pointer, it ALWAYS sees it as 'void(*)(int*)' (for example), rather than 'void(int*)' and fails to compile. For example, the following program: #include <boost/function.hpp> void SomeFunc(int* Blah) { //DoSomething } template<typename Signature> boost::function<Signature> GetFunction(Signature ToCall) { //TODO: Check if function is in list, add it to list, etc. return boost::function<Signature>(ToCall); } int __cdecl main(int argc, char* argv[], char* envp[]) { GetFunction(SomeFunc); } I get: (Project Directory)\boostfunctest.cpp(17) : error C2027: use of undefined type 'boost::function' with [ Signature=void (__stdcall *)(int *), Allocator=std::allocator ] So, anyone have any idea what's wrong and how to fix it? Thanks for any help. Note: I am compiling with /Gz, but compiling with /Gd and /Gr merely changes the "__stdcall" to "__cdecl" and "__fastcall" in the error messages, respectively, so it does not seem to matter which calling convention is used. -- Erzengel des Lichtes 光の大天使 (Hikari no Daitenshi) Archangel of Light

2 2

Passing Mutexes
by Simon Pickles 31 Jul '08

31 Jul '08

Hi, I am trying to implement a simple producer/consumer system with two or more threads. The main thread has a consumer class which creates producers. These producers perform synchronous blocking operations then post their outcome into a std::vector of results which was passed from the main consumer. class consumer { public: consumer() { m_results = boost::shared_ptr<std::vector<result> >( new std::vector<result> ); new producer( m_results, m_mutex ); // do a single task and put result in m_results } void Process() { result r; { boost::mutex::scoped_lock lock(m_mutex); r = m_results.pop.front(); } // Do stuff with r } private: boost::mutex m_mutex; boost::shared_ptr<std::vector<result> > m_results; }; class producer { producer( boost::shared_ptr<std::vector<result> > results, boost::mutex& mtx ) { boost::thread( boost::bind( &DoInThread, this, results, mtx ) ); // actually uses a threadpool but not relevant here. } void DoInThread( boost::shared_ptr<std::vector<result> > results, boost::mutex& mtx ) { result r; // do long async op and store in r boost::mutex::scoped_lock lock(mtx); results->push_back(r); } }; /////////////// I am trying to share a single mutex with both producer and consumer. However I get a noncopyable error, even if I pass a reference. Can anyone point out what the correct approach is? Thanks Simon

3 4

Re: [Boost-users] Array to List
by noman javed 31 Jul '08

31 Jul '08

Actually I am working on numerical data.

3 2

Xpressive and line breaks
by Simon Steele 30 Jul '08

30 Jul '08

Hi, I think there's a bug in Xpressive in Boost 1.35 with newline handling. Here is a very simple example: Subject: abc\ndef\nghi Regex: ^.+$ I'm looking for "abc". The following xpressive-based code has odd results: string text(argv[1]); sregex rex = sregex::compile(text, regex_constants::not_dot_newline); smatch match; string subject("abc\ndef\nghi"); if (regex_search(subject.begin(), subject.end(), match, rex, regex_constants::match_default)) { std::cout << "Match at: " << match.position(0) << " length: " << match.length(0); } ^.+$: Match at: 8 length: 3 $: Match at: 4 length: 0 .$: Match at: 10 length: 1 These definitely aren't right, it appears that the only place where end-of-line is matching is at end-of-string. Things get even stranger if I try to use Windows or Mac style end-of-line characters which I need to support too. If I use boost::regex instead then I get these results: ^.+$: Match at: 0 length: 3 $: Match at: 3 length: 0 .$: Match at: 2 length: 1 These are the results I'd expect. It appears in Xpressive that the check in assert_line_base::is_line_break is broken, the following line: if(traits_cast<Traits>(state).isctype(ch, this->newline_)) checks the previous character to see if it's a line break. I believe this should check the current character: if(traits_cast<Traits>(state).isctype(*state.cur_, this->newline_)) This then gets me sane results: ^.+$: Match at: 0 length: 3 $: Match at: 3 length: 0 .$: Match at: 2 length: 1 Is this a known bug? Thanks, Simon.

2 3

[Conversion] imprecision with lexical_cast from double to std::string
by Andreas Ries 30 Jul '08

30 Jul '08

Hi, I'm using the borland toolset 5.8.2 under Win XP and have a problem doing the following: double val = 795.6352; string result = boost::lexical_cast <string> (val); the resulting string is: "795.63520000000005" with boost 1_35_0 the resulting string is: "795.6352000000001" with boost_1_34_0 Can anybody help?

3 2

dll-interface problems
by Andrej van der Zee 30 Jul '08

30 Jul '08

Hi, I am not much of a Windows programmer, so I have a basic question. I want to make a library that (among other stuff) defines an exception like this: #include <boost/exception/exception.hpp> namespace speedo { typedef boost::error_info<struct tag_error, unsigned> error_info; class __declspec(dllexport) exception : public boost::exception { }; } When I try to compile this, I get the following warning: c:\cygwin\home\andrej\speedo\trunk\util\exception.h(14) : warning C4275: non dll-interface class 'boost::exception' used as base for dll-interface class 'speedo::exception' C:\cygwin\home\Andrej\speedo\trunk\boost/exception/exception.hpp(47) : see declaration of 'boost::exception' c:\cygwin\home\andrej\speedo\trunk\util\exception.h(13) : see declaration of 'speedo::exception' Is this a problem, and, how do I get rid of this without changing the boost-exception lib itself? Cheers, Andrej __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

5 4

Reading a file with filesystem
by Simon Pickles 30 Jul '08

30 Jul '08

Hi Say I want to copy the contents of a file into memory, how do I do the actual copy. Eg boost::filesystem::path p = "file.txt" const unsigned int filesize = boost::filesystem::file_size( p ); unsigned char* buffer = new unsigned char[filesize]; // how do I copy file contents into buffer? Many thanks Simon

2 1

boost::date_time
by Husain Das 30 Jul '08

30 Jul '08

I am using Visual C++ 9.0 2008 Express Edition with the pre-built boost libraries ver 1.35.0 for Windows . I am using the date_time functions from boost. Everything works fine till i decided to print the date objects through the to_simple_string(date) function . I receive the below linker errors . Can you guys advise me whats wrong ? public: char const * __clrcall boost::gregorian::greg_month::as_long_string(void)const " (?as_long_string@greg_month@gregorian@boost@@$$FQBMPBDXZ) referenced in function "public: static class std::basic_ostream<char,struct std::char_traits<char> > & __clrcall boost::date_time::month_formatter<class boost::gregorian::greg_month,class boost::date_time::iso_format<char>,char>::format_month(class boost::gregorian::greg_month const &,class std::basic_ostream<char,struct std::char_traits<char> > &)" (?format_month@?$month_formatter@Vgreg_month @gregorian@boost@@V?$iso_format@D@date_time@3@D@date_time@boost@ @$$FSMAAV?$basic_ostream@DU?$char_traits@D@std@@@std@ @ABVgreg_month@gregorian@3@AAV45@@Z) 1>ADONET_Example.obj : error LNK2028: unresolved token (0A00007D) "public: char const * __clrcall boost::gregorian::greg_month::as_short_string(void)const " (?as_short_string@greg_month@gregorian@boost@@$$FQBMPBDXZ) referenced in function "public: static class std::basic_ostream<char,struct std::char_traits<char> > & __clrcall boost::date_time::month_formatter<class boost::gregorian::greg_month,class boost::date_time::iso_format<char>,char>::format_month(class boost::gregorian::greg_month const &,class std::basic_ostream<char,struct std::char_traits<char> > &)" (?format_month@?$month_formatter@Vgreg_month @gregorian@boost@@V?$iso_format@D@date_time@3@D@date_time@boost@ @$$FSMAAV?$basic_ostream@DU?$char_traits@D@std@@@std@ @ABVgreg_month@gregorian@3@AAV45@@Z) 1>ADONET_Example.obj : error LNK2019: unresolved external symbol "public: char const * __clrcall boost::gregorian::greg_month::as_long_string(void)const " (?as_long_string@greg_month@gregorian@boost@@$$FQBMPBDXZ) referenced in function "public: static class std::basic_ostream<char,struct std::char_traits<char> > & __clrcall boost::date_time::month_formatter<class boost::gregorian::greg_month,class boost::date_time::iso_format<char>,char>::format_month(class boost::gregorian::greg_month const &,class std::basic_ostream<char,struct std::char_traits<char> > &)" (?format_month@?$month_formatter@Vgreg_month @gregorian@boost@@V?$iso_format@D@date_time@3@D@date_time@boost@ @$$FSMAAV?$basic_ostream@DU?$char_traits@D@std@@@std@ @ABVgreg_month@gregorian@3@AAV45@@Z) 1>ADONET_Example.obj : error LNK2019: unresolved external symbol "public: char const * __clrcall boost::gregorian::greg_month::as_short_string(void)const " (?as_short_string@greg_month@gregorian@boost@@$$FQBMPBDXZ) referenced in function "public: static class std::basic_ostream<char,struct std::char_traits<char> > & __clrcall boost::date_time::month_formatter<class boost::gregorian::greg_month,class boost::date_time::iso_format<char>,char>::format_month(class boost::gregorian::greg_month const &,class std::basic_ostream<char,struct std::char_traits<char> > &)" (?format_month@?$month_formatter@Vgreg_month @gregorian@boost@@V?$iso_format@D@date_time@3@D@date_time@boost@ @$$FSMAAV?$basic_ostream@DU?$char_traits@D@std@@@std@ @ABVgreg_month@gregorian@3@AAV45@@Z) 1>D:\Profiles\g18244\My Documents\Visual Studio 2008\Projects\DataSet\Debug\ADONET_Example.exe : fatal error LNK1120: 4 unresolved externals

2 1

Array to List
by noman javed 30 Jul '08

30 Jul '08

I have two questions How can we convert an array (arbitrary type, arbitrary size) to mpl::list. Is there any metafunction in mpl which can do this for us ? Second is there any way to send mpl::list (or any mpl sequence) to MPI_Alltoallv without converting it into an array ?

2 1

boost program options and notifier call
by Aljaz 30 Jul '08

30 Jul '08

Hello I have boost.program_options implemented inside a config class. I want to call function (my_function) that is a member of config class for specific option (with notifier call). class config_class { public: void read_config() { po::options_description desc("Allowed options"); desc.add_options() ("help", "produce help message") ("include-path,I", po::value< vector<string> >()->notifier(&config_class::my_function), "include path"); } void my_function(vector<std::string> str) { } }; This wont compile and will give error for ..>()->notifier(&config_class::my_function)... >> error C2064: term does not evaluate to a function taking 1 arguments What am I doing wrong? Many thanks in advance! Aljaz

3 3

boost::serialization - PHP -> c++ (fastcgi)
by Alejandro Martinez 30 Jul '08

30 Jul '08

What i need to do is this: Have a php file in a webserver, doing a POST with binary payload to a fast-cgi written in c++, and the c++ should deserialize that payload into a known struct. something like: struct whatever { int a; int b; float c; std::vector<int> d; } (mainly structs consisting of basic types and collections of basic types) I've been playing around with boost::serialization, but i can't seem to comprehend the binary format it generates (So i could hardcode the php to make a valid payload to be deserialised from the fast-cgi). And not so important: i've noticed boost::serialization to binary archives always look like: serialization::archive ÃõH@ can't i get rid of the "serialization::archive" thing that is obviusly not part of the struct i just serialized? Thanks a lot for your help. I'd appreciate any other ideas to accomplish the same result :).

2 2

boost.asio and ncurses.h problem
by Ruben Lara 30 Jul '08

30 Jul '08

Hi all... If i try to compile boost.asio and ncurses.h together i get next problem: bermejo@BERMEJO-MOBILE ~/Proyecto/boost $ g++ -lncurses -lboost_system -lboost_thread -o main *.cpp /usr/include/boost/asio/detail/socket_option.hpp:242: error: ‘stdscr’ is not a type /usr/include/boost/asio/detail/socket_option.hpp:252: error: ‘stdscr’ is not a type /usr/include/boost/asio/detail/socket_option.hpp:252: error: expected identifier before ‘)’ token bermejo@BERMEJO-MOBILE ~/Proyecto/boost $ Problem when: #include <boost/asio.hpp> #include <ncurses.h> Any ideas? Thank you in advance Rubén Lara _________________________________________________________________ La última hora de tu ciudad en MSN Noticias http://noticias.es.msn.com/

1 0

Boost spirit: overlapping inner struct result
by Pascal Kesseli 30 Jul '08

30 Jul '08

Hi everyone When trying to compile the serialization library for my Montavista embedded computer, I am getting a strange error message concerning boost spirit/core/primitives/numerics.hpp stating that struct result in sign_parser has already been defined before. Back then, I couldn't deny that fact, as result is already defined in sign_parser's superclass parser, so I renamed the struct in the subclass to tresult and the library compiled fine. Currently, I am asking myself what influence such a change might have on the running program. I am having unexplainable SIGABRT signals appearing and killing my program, thus I suspect my change was not that mere after all. Is there a better workaround I could use to solve this problem? Thanks in advance for your replies and best regards Pascal Kesseli PS: g++ --version is for my compiler: g++ (GCC) 3.4.3 (MontaVista 3.4.3-25.0.30.0501131 2005-07-23) Copyright (C) 2004 Free Software Foundation, Inc. Dies ist freie Software; die Kopierbedingungen stehen in den Quellen. Es gibt KEINE Garantie; auch nicht für VERKAUFBARKEIT oder FÜR SPEZIELLE ZWECKE. PPS: The compiler error message (quite self-explanatory, even though having some german phrases in it): Building file: ../xml_grammar.cpp Invoking: GCC C++ Compiler g++ -O0 -Wall -c -fmessage-length=0 -MMD -MP -MF"xml_grammar.d" -MT"xml_grammar.d" -o"xml_grammar.o" "../xml_grammar.cpp" In file included from ../basic_xml_grammar.ipp:22, from ../xml_grammar.cpp:63: /usr/local/xscale_be/bin/../target/usr/include/boost/spirit/core/primitives/numerics.hpp:122: Fehler: Deklaration von »template<class ScannerT> struct boost::spirit::sign_parser::result« /usr/local/xscale_be/bin/../target/usr/include/boost/spirit/core/parser.hpp:123: Fehler: steht mit der vorherigen Deklaration »template<class ScannerT> struct boost::spirit::parser<boost::spirit::sign_parser>::result« in Konflikt make: *** [xml_grammar.o] Fehler 1

2 1

[serialization] : NVP macros and template classes
by Mathieu Peyréga 30 Jul '08

30 Jul '08

Hello, I have a template class as a base class I wish to serialize... In that case, the BOOST_SERIALIZATION_BASE_OBJECT_NVP does not work as it introduce < > caracters wich i guess are forbidden in the xml tag... Is there a nice way to solve this issue ? For now, I am only facing the 1 parameter case and thus defined a macro : #define BOOST_SERIALIZATION_BASE_OBJECT_TEMPLATE_NVP(classname,templateparameter) \ boost::serialization::make_nvp( \ BOOST_PP_STRINGIZE(classname)BOOST_PP_STRINGIZE(templateparameter), \ boost::serialization::base_object<classname<templateparameter> >(*this) \ ) which gives me somme acceptable behaviour... if I have ClassA<ParameterClass> as a base class I write BOOST_SERIALIZATION_BASE_OBJECT_TEMPLATE_NVP(ClassA,ParameterClass) instead of "usual" BOOST_SERIALIZATION_BASE_OBJECT_NVP(BaseClassName) Regards, Mathieu -- http://www.incub.net

1 0

Re: [Boost-users] [boost.thread] destruction of condition variables
by Vladimir Pozdyaev 30 Jul '08

30 Jul '08

Howard Hinnant: > For the moment consider that all mutex and cv operations are atomic. > They can not be interrupted (as if they were a single machine > instruction). In this model your code is still not safe. You have a > race: Does the cv get destructed before cv.notify_all() is called? > The answer is that we don't know. If it does, you have undefined > behavior. You would be referencing a member of a destructed object. > > Can you construct code that will reliably test your question? Your > current code does not. If your question can not be tested, then the > answer becomes irrelevant. > > To be clear, your original code would be just as "correct" if you > commented out the cv.wait(l) in ~C(). Because of spurious wakeups, > this call to wait does not *reliably* have any effect whatsoever. It doesn't seem possible to isolate the original problem without introducing SW-related issues, so from the practical point of view your reasoning is perfectly understandable, thanks for clarification. What irks me here, is that even when there are no "bug-activating" events (read, SW), and the sequence of executed instructions does not violate the specs in any way, the program is still allowed to fail. From the practical point of view, I agree, it doesn't matter. From the logical point of view though, I can't help noticing the inconsistence, since it is exactly "executed instructions" (program behaviour for each particular run, that is, not the source code as such, however many other issues might be in there) that the specs are talking about: "being in such-and-such state, we are allowed to execute such-and-such actions". ---- Vladimir

1 0

[Boost.Fusion] Compile-time callbacks.
by Vjekoslav Brajkovic 30 Jul '08

30 Jul '08

Hi, I am somewhat new to Boost Fusion and MPI, therefore I apologize if I am asking a trivial question (I wasn't able to the answer). I have a map of <mpl::int_<N>, boost::function> pairs. Each integer is a command, and based on that command I would like call some specific function. However, after debugging through the code, I have realized that the callbacks are not compile time. So, I was wondering if anybody could tell me if there is a way of modifying my code in such a manner that there is no run-time overhead associated with map indexing. Here is an example code. ////////10////////20////////30////////40////////50////////60////////70////////80 int main(int argc, char* argv[]) { boost::function<void (int)> _int_1_; boost::function<void (std::string)> _int_2_; _int_1_ = &fun_1; _int_2_ = &fun_2; { using boost::fusion::map; using boost::mpl::int_; boost::fusion::result_of::make_map<int_<1>, int_<2>, boost::function<void (int)>, boost::function<void (std::string)> >::type fmap; boost::fusion::at_key< int_<1> >(fmap) = _int_1_; boost::fusion::at_key< int_<1> >(fmap)(5); }

3 6

Converting tuples
by Orhun Birsoy 29 Jul '08

29 Jul '08

Hi, I have a function that is templated with a tuple. I would like to convert the input tuple to a different tuple with the same size, and with related but different types. I can have any number of items in the tuple, not just two as given in the example. ie tuple<shared_ptr<Foo>, shared_ptr<Bar>> r = GetProperties<tuple<Foo, Bar>>(); The template magic that will achive this currently eludes me. How can I do this? Thanks. -- Orhun Birsoy

2 1

boost::lambda to replace a for loop
by Meryl Silverburgh 29 Jul '08

29 Jul '08

Hi, Can you please tell me if there is an easy way to replace the following for loop using boost:lambda? I have a vector of A, i want to call 'aMethod of each A, and stop it when one of them return true. for (vector<A*>::const_iterator iter = aList.begin() ; iter != aList.end(); ++iter) { A* anA = (*iter); // break out the for loop if aMethod return true; if (anA->aMethod()){ break; }

5 5

[Boost.Serialization] Deserialization of very small doubles
by Markus.Himmerich＠oppenheim.de 29 Jul '08

29 Jul '08

Hi, I am using the Serialization library version 1.33 with MSVC 2003. From the serialization of a class with an uninitialized double member "a" I got the following XML: <a>1.0198947755763149e-312</a> When I deserialize this number I get a stream_error. Is this a bug? Best regards. Markus </PRE> <meta content="text/html; charset=ISO-8859-1" Diese E-Mail und eventuell beigefügte Anhänge enthalten vertrauliche Informationen, die rechtlich besonders geschützt sein können, zum Beispiel durch das Bankgeheimnis. Diese Informationen sind ausschließlich für die als Adressaten genannten Personen bestimmt. Wenn Sie nicht der angeschriebene Empfänger sind oder diese E-Mail durch einen Übertragungsfehler erhalten haben, informieren Sie uns bitte sofort per E-Mail, Telefon oder Telefax und löschen danach die vorliegende E-Mail. Das unbefugte Kopieren dieser E-Mail, ihrer eventuell beigefügten Anhänge sowie die unbefugte Weitergabe der enthaltenen Informationen an Dritte sind nicht gestattet. Wir danken für Ihre Hilfe. This e-mail message together with its attachments, if any, is confidential and may contain information subject to legal privilege, e.g. banking secrecy. The information contained in this e-mail or its attachments is intended solely for the persons named as addressees. If you are not the intended recipient or have received this e-mail in error, please advise us immediately by e-mail, telephone or fax and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. Thank you for your co-operation. <PRE>

2 1

Re: [Boost-users] dll-interface problems
by Andrej van der Zee 29 Jul '08

29 Jul '08

Yes okay, but how do you then export these methods from the base class if they appear in an external library (boost::exception in this case), without changing the external library? Cheers, Andrej ----- Original Message ---- From: gast128 <gast128(a)hotmail.com> To: boost-users(a)lists.boost.org Sent: Tuesday, 29 July, 2008 6:09:37 AM Subject: Re: [Boost-users] dll-interface problems Andrej van der Zee <mavdzee <at> yahoo.co.uk> writes: > #include <boost/exception/exception.hpp> > > namespace speedo { > > typedef boost::error_info<struct tag_error, unsigned> error_info; > > class __declspec(dllexport) exception : public boost::exception > { > }; > > } > > When I try to compile this, I get the following warning: > > c:\cygwin\home\andrej\speedo\trunk\util\exception.h(14) : warning C4275: non dll-interface class > 'boost::exception' used as base for dll-interface class 'speedo::exception' > C:\cygwin\home\Andrej\speedo\trunk\boost/exception/exception.hpp (47) : see declaration of 'boost::exception' > c:\cygwin\home\andrej\speedo\trunk\util\exception.h(13) : see declaration of 'speedo::exception' > > Is this a problem, and, how do I get rid of this without changing the boost- exception lib itself? The exported attribute indicates that all functions from the class are exported. The warning is that you can potentially call a non exported function from the base class, e.g.: struct public Base { void Foo1(); //impl. in cpp }; struct __declspec(dllexport) Derived : public Base { void Foo2(); //impl. in cpp }; void Foo() { Derived d; d.Foo1(); //error, but at least a linker error d.Foo2(); } wkr, me _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

2 1

[tokenizer] simple way to iterate over wrods in a string?
by frederic.bron＠alcan.com 29 Jul '08

29 Jul '08

I find that tokenizer is rather complicated to use when the separators in a string are not the standard whites. I am looking at something that would simply give : for (some_iterator word=word_begin(s, ";!") ; word!=word_end() ; ++word) { /* */ } I have written the following code which works well but I wonder why. My questions are : 1.) the object "tokens" created in function wbegin(...) is deleted when the function exists; is it an issue when iterating over the elements? 2.) I use default constructor of the iterator as end iterator; is it legal? This allows me not to provide 2 times the string and the list of separators. F. Bron #include <iostream> #include <string> #include <boost/tokenizer.hpp> typedef boost::tokenizer< boost::char_separator<char> >::iterator const_witerator ; const_witerator wbegin(const std::string &s, const char *separators=" \t\n\f\r\v") { boost::tokenizer< boost::char_separator<char> > tokens(s, boost::char_separator<char>(separators)) ; return tokens.begin() ; } const_witerator wend() { return const_witerator() ; } int main() { std::string s(" a; bc ;def;ghi") ; // -> [ a][ bc ][def][ghi] for (const_witerator w=wbegin(s, ";") ; w!=wend() ; ++w) { std::cout << '[' << *w << ']' ; } std::cout << '\n' ; // -> [a][bc][def][ghi] for (const_witerator w=wbegin(s, " ;") ; w!=wend() ; ++w) { std::cout << '[' << *w << ']' ; } std::cout << '\n' ; return 0 ; } 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

BGL undirected graph
by Line Blander Reinhardt 29 Jul '08

29 Jul '08

Hi all I have a problem with an graph which is undirected. I thought that this meant that an edge (u,v) was the same as an edge (v,u) however when I insert (u,v) into a map and later asks the map to find (v,u) then the map does not find it. s=edge(target(*oei,graph_),source(*oei,graph_),graph_).first; EMap.insert(EdgeElementPair(s,p)); Esp=NULL; s=edge(source(*oei,graph_),target(*oei,graph_),graph_).first; Esp = EMap[s]; how can this be???? My graph is: typedef boost::adjacency_list<boost::vecS, boost::vecS, boost::undirectedS, VertexProperties, EdgeProperties, GraphProperties> Graph; Thanks Line

1 0

Re: [Boost-users] [boost.thread] destruction of condition variables
by Vladimir Pozdyaev 29 Jul '08

29 Jul '08

Howard Hinnant: > On Jul 28, 2008, at 6:49 AM, Vladimir Pozdyaev wrote: > > > > Looking at, e.g., > http://www.opengroup.org/onlinepubs/009695399/functions/pthread_cond_init.h… > > reveals that "It shall be safe to destroy an initialized condition > > variable upon which no threads are currently blocked." Am I right in > > understanding that the wait-destroy sequence should be quite safe > > this way (provided no one else waits)? > > I believe your code as shown is subject to "spurious wakeup". If the > wait ends (spuriously) before the notify_all() completes, or is even > initiated, then the notify happens on a destructed cv. POSIX says > that in this case the pthread_cond_broadcast will return EINVAL. I believe I should apologise for this distraction. I am aware of possibility of spurious wakeups; they are one reason for the claim that the original code is not an example of good practice. The point is, spurious wakeups have nothing to do with the problem at hand, so I just opted for a more concise code sample. > The sentence you refer to means that the thread doing the notifying > can safely destroy the cv even if the waiting thread has not yet > returned from the wait (as long as that thread or any other do not try > to initiate a new wait after the final signal/broadcast). Note though This is a somewhat narrower interpretation, since the original sentence does not consider roles of threads (notifying or waiting). Is it a matter of bad wording on the part of the latter? Because I don't see in what way does my code contradict the condition "no threads are currently blocked" (on a cv). AFAICT, after the only cv.wait has finished... > that it is not safe to destruct the mutex which is being waited on, > until the waiting thread wakes from the wait (locking the mutex) and > then unlocks that mutex. ... and the only (scoped) lock on a mutex released, no threads are blocked on them, so it shouldn't be problematic to destroy both mutex and cv, should it? (The problem doesn't seem to reproduce with a trunk version of the lib, so the point may well be moot anyway, but still I'm wondering...) ---- Vladimir

2 1

[CRC] Compilation fails with #include <boost/crc.hpp>
by Norbert Riedlin 29 Jul '08

29 Jul '08

Hi all, I want to use boost CRC, but when I #include <boost/crc.hpp>, I get the following error: "error: ISO C++ forbids variable-size array 'table_type'" in line 468 of crc.hpp. gcc --version tells me, I'm using the following gcc on my Mac (OSX 10.5): "i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5484)" I use boost 1.34.1, but as crc.hpp of version 1.35 does not differ, I suppose updating the library would not help. The error is in the following context: <code> struct crc_table_t { BOOST_STATIC_CONSTANT( std::size_t, byte_combos = (1ul << CHAR_BIT) ); typedef mask_uint_t<Bits> masking_type; typedef typename masking_type::fast value_type; #if defined(__BORLANDC__) && defined(_M_IX86) && (__BORLANDC__ == 0x560) // for some reason Borland's command line compiler (version // 0x560) // chokes over this unless we do the calculation for it: typedef value_type table_type[ 0x100 ]; #else typedef value_type table_type[ byte_combos ];//<-- error here #endif static void init_table(); static table_type table_; }; // boost::detail::crc_table_t </code> I suppose it has to do with a bug of gcc, that cannot calculate "byte_combos" at compile time (or at least it acts as if it had to calculate "byte_combos" at runtime). A fix would be to enhance the "#if defined..." to the gcc versions with the said bug. I just realized there was an entry in the bug tracking system at sourceforge concerning this problem: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1478435&gro up_id=7586 but I have no permission to view the issue. The entry was made in early 2006. Is there any work on this issue? TIA Norbert P.S.: I also realize I can get around the problem by not using "-pedantic", but for me this is a valuable switch.

2 1

[BOOST::ASIO] How can I catch disconnect event from remote side ?
by Ken zhang 29 Jul '08

29 Jul '08

Hi Dear all. How can I catch the disconnect event from remote side in boost::asio? Thanks

2 1

Specifying which version of gcc to use when compiling boost
by Simon Lacroix 29 Jul '08

29 Jul '08

Hello all, I have a system with both gcc version 3.4 and gcc version 3.2 installed (distro is RHE4). I am trying to compile the filesystem package using 3.2 but for some reason it always seem to pick gcc 3.4. I tried the following (as specified in section 5.2.2 of the unix getting started guide) : ./configure .. -with-toolset=gcc-3.2.3 Performing a make after that tells me that it doesn't know anything about the tool and then give me a list of tool (basically all tools name with no version) Doing this however works but it uses version 3.4 ./configure .. -with-toolset=gcc Both cc and gcc executable points to gcc 3.2.3 the version that I want to use. Anybody can point me out what I am missing ? Thanks in advance ! Simon

3 2

Re: [Boost-users] compiling boost on AIX gives pthread errors
by Andrej van der Zee 29 Jul '08

29 Jul '08

Hi, > We are using AIX 5.3 and the 4.2.0 compiler and obviously require IBM's mpCC > MPI compiter to be supported, out-of-the-box. You should not be using the gcc compiler that is shipped with AIX 5.3 because it is hopelessly broken, just like their alternative binary version from the official IBM website. I wonder why? Note that IBMs compiler xlc/c++ costs almost 4000 Euro's for one user's lisence. And still I wonder why they ship a broken gcc compiler with their AIX distribution ;) Luckily you also can get binary distrubutions from here: http://gcc.gnu.org/install/binaries.html. Besides that there is a patch you should apply to the Boost source tree to make it all work (or you can use boost-trunk from SVN). Then you will be able to compile boost on AIX 5.3, but you will get some occasional complains from the linker and/or compiler. Anyway, I would be greatful if Boost would officially start to support gcc on AIX! Hopefuly it will be picked up soon... Cheers, Andrej __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

2 1

XML library?
by Michiel Helvensteijn 29 Jul '08

29 Jul '08

I was surprised not to find an XML parser/generator library in boost. Or is it hidden somewhere? Is it planned for a future release, perhaps? In the meantime, can anyone recommend another open source C++ XML library I can use (with DOM parser)? Thanks! -- Michiel Helvensteijn

8 10

Re: [Boost-users] compiling boost on AIX gives pthread errors
by Henrik Nagel 29 Jul '08

29 Jul '08

K. Noel Belcourt wrote: > > We don't test with gcc on Aix, but we should. > I am having trouble installing boost 1.35.0 on AIX too. How about porting boost to AIX? We have an IBM p575+ computer with AIX that you can get an account on for testing purposes. We are using AIX 5.3 and the 4.2.0 compiler and obviously require IBM's mpCC MPI compiter to be supported, out-of-the-box. Best regards, Henrik -- View this message in context: http://www.nabble.com/compiling-boost-on-AIX-gives-pthread-errors-tp1733930… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

Suggestions for Simple Expression Evaluation
by Richard L. Aurbach 28 Jul '08

28 Jul '08

I am looking for some code to handle simple expression evaluation -- cases like "a | b | c", or "(a + b)/2", where 'a', 'b', and 'c' are named constants that I can evaluate by lookup. I.e., code to evaluate simple expressions to produce integer results. I'm looking for something light-weight and easy to use -- something that justifies a decision to look elsewhere rather than writing the 10- million-and-first simple evaluator. (I know that lots of folks have written this type of code as a homework assignment in a data structures course. As it happens, I don't have an old assignment to look up and am hoping to spare the time doing it now :-) ) I didn't see anything in the boost library that didn't appear to be incredible overkill, but I'm happy to be proven wrong about that. Anyway, I would be very interested in some suggestions (using boost or otherwise) that can help me implement run-time evaluation of simple expressions without a major investment in the size or complexity of my application. Cheers, Rick Aurbach Aurbach & Associates, Inc.

2 1

new version
by Gang Ma 28 Jul '08

28 Jul '08

Thanks, guys. I change my code a bit. The results are right. But I suspect it never used thread, but excute the thread one by one. new code void mtread(char* filename,const int stidx, const int edidx,int id) { fstream infile; infile.open(filename); string line; int linenum = 0; if (infile.good()){ while (! infile.eof()) { boost::mutex::scoped_lock lock(io_mutex); // infile.seekg(linenum,ios::beg); getline(infile,line); if (linenum>=stidx && linenum<=edidx){ cout<<id << " : " <<line<<endl; //cout<<linenum<<endl; linenum++; } else { linenum++; if (linenum>edidx) break; } } } else { cerr<< "file " << filename << " cannot be opened for reading" <<endl; } infile.close(); } I got the same results running the program twice. 1 : 1 1 : 2 1 : 3 1 : 4 1 : 5 2 : 6 2 : 7 2 : 8 2 : 9 2 : 10 Thank for your helps. regards, gma

1 0

Re: [Boost-users] Initialization of boost::asio::ip::tcp::socket geneates unhandled exception
by Igor R 28 Jul '08

28 Jul '08

Hi, The problem is somewhere in the design of your program, so it's hardly possible to find out it from this short description. Sounds like dangling reference/pointer - probably, io_service was destroyed/not initialized yet? (remember that the members are initialized in the order of their definition) 2008/7/28, Jean-Sebastien Stoezel <js.stoezel(a)gmail.com>: > Hi, > > I'm getting confused by the unhandled exception I get when > initializing a TCP socket. This happens when the socket is > instantiated and initialized with an IO service object, from the > constructor of a class called CProcessor. > > Here are the variables declaration, inside the class: > > boost::asio::ip::tcp::socket m_Socket; > boost::asio::io_service m_IoService; > > Here is what the default constructor looks like for this class: > CProcessor::CProcessor(void): > m_Socket(m_IoService) > {} > > The exception is generated by this constructor, as soon as the > m_Socket object is initialized. > > The type of unhandled exception I got is as follow: > "Unhandled exception at whatever in hatever.exe: 0xC0000005: Access > violation reading location 0xcccccce0." > The program breaks in win_mutex.hpp, at a line calling: > ::EnterCriticalSection(&crit_section_); > > I run VS9. > > Any idea?! > > Thanks, > Jean > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 1

Release 1.36.0 Beta
by Lothar Werzinger 28 Jul '08

28 Jul '08

Hi, on http://www.boost.org/community/index.html kit indicates that 1.36.0 Beta should be available. However I found no link on the news or download page. Where can I get the beta? Don't you want the beta to be tested by a wider audience? How would you do that if it is not publicly available? Lothar -- Lothar Werzinger Dipl.-Ing. Univ. framework & platform architect Tradescape Inc. - Enabling Efficient Digital Marketplaces 1754 Technology Drive, Suite 128 San Jose, CA 95110 web: http://www.tradescape.biz

3 3

multithreaded read a file using thread lib
by Gang Ma 28 Jul '08

28 Jul '08

Hi, I tried to use boost/thread library to write a program to read a large text file. The program compiled but did not get the right answer. I am not sure my usage of the library is correct. I appreciate your helps. Here are the code: #include <iostream> #include <fstream> #include <string> #include <boost/thread/thread.hpp> #include <boost/thread/mutex.hpp> #include <boost/bind.hpp> #include <SQLAPI.h> //#include "stdafx.h" boost::mutex io_mutex; using namespace std; void mtread(char* filename,const int stidx, const int edidx,int id) { fstream infile; infile.open(filename); string line; if (infile.good()){ for (int linenum=stidx; linenum<=edidx;linenum++) { boost::mutex::scoped_lock lock(io_mutex); infile.seekg(linenum,ios::beg); getline(infile,line); cout<<id << " : " <<line<<endl; } } else { cerr<< "file " << filename << " cannot be opened for reading" <<endl; } infile.close(); } int main(int argc, char** argv){ boost::thread thrd1(boost::bind(&mtread, argv[1],0,4,1)); boost::thread thrd2(boost::bind(&mtread, argv[1],5,9,2)); thrd1.join(); thrd2.join(); return 0; } I would like thread1 read linie 0-4 and thread2 read line 5-9. My dummy test file has 10 lines, each line is 1,2, 3...,10 etc. My output is 2 : 2 : 3 2 : 2 : 1 : 1 1 : 1 : 1 : 2 1 : 2 : 4 regards, Gang Ma

4 3

Initialization of boost::asio::ip::tcp::socket geneates unhandled exception
by Jean-Sebastien Stoezel 28 Jul '08

28 Jul '08

Hi, I'm getting confused by the unhandled exception I get when initializing a TCP socket. This happens when the socket is instantiated and initialized with an IO service object, from the constructor of a class called CProcessor. Here are the variables declaration, inside the class: boost::asio::ip::tcp::socket m_Socket; boost::asio::io_service m_IoService; Here is what the default constructor looks like for this class: CProcessor::CProcessor(void): m_Socket(m_IoService) {} The exception is generated by this constructor, as soon as the m_Socket object is initialized. The type of unhandled exception I got is as follow: "Unhandled exception at whatever in hatever.exe: 0xC0000005: Access violation reading location 0xcccccce0." The program breaks in win_mutex.hpp, at a line calling: ::EnterCriticalSection(&crit_section_); I run VS9. Any idea?! Thanks, Jean

2 1

How to tokenize a string with substring as separators?
by Sunsawe 28 Jul '08

28 Jul '08

Hi, I would like to tokenize a string by specifying substrings as separators. So far, i only found the split function with is_any_of as argument. But is_any_of considers every character and not a (or some) substring. Would it be possible to add substrings to the already "well-known" separators (blanks...)? Thanks -- View this message in context: http://www.nabble.com/How-to-tokenize-a-string-with-substring-as-separators… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

Re: [Boost-users] [boost.thread] destruction of condition variables
by Vladimir Pozdyaev 28 Jul '08

28 Jul '08

Anthony Williams: > > "Peter Dimov" <pdimov(a)pdimov.com> writes: > > > Anthony Williams: > > > >> However, it is never safe to destroy any object whilst another thread > >> might still be in a member function. > > > > I believe that this is a "POSIX destruction safety" issue. POSIX CVs > > are supposed to support such code. > > POSIX CVs are supposed to support broadcast immediately before > destroy. What we have here is the waiting thread doing the > destruction, which is not guaranteed safe by POSIX, as far as I know. > > Looking at, e.g., http://www.opengroup.org/onlinepubs/009695399/functions/pthread_cond_init.h… that "It shall be safe to destroy an initialized condition variable upon which no threads are currently blocked." Am I right in understanding that the wait-destroy sequence should be quite safe this way (provided no one else waits)? ---- Vladimir

2 1

transform view
by noman javed 28 Jul '08

28 Jul '08

I want to apply some arbitrary function F on each element of a sequence through myfun class inherited from transform_view. I am unable to output the elements of the resultant sequence. Below is the whole code of my program #include <boost/mpl/int.hpp> #include <boost/mpl/apply.hpp> #include <boost/mpl/list_c.hpp> #include <boost/mpl/for_each.hpp> #include <boost/mpl/transform_view.hpp> #include <iostream> using namespace boost::mpl; namespace mpl = boost::mpl; struct mysquare { template< typename U > void operator()(U x) { static const int value = x*x; } }; struct value_printer { template< typename U > void operator()(U x) { std::cout << x << " "; } }; template<class F, class Seq> struct myfun:transform_view<Seq,F> {}; int main() { using namespace std; typedef list_c<int,0,1,2,3,4,5> numbers; typedef myfun<mysquare,numbers>::type newnum; for_each<numbers>(value_printer()); // for_each<newnum>(value_printer()); // I don,t know what transform_view return }

2 1

Re: [Boost-users] run_test parameter not working (Boost Unit Test Framework)
by Marc Oliver Castañeda 28 Jul '08

28 Jul '08

Hi Gennadiy, Will this be released as a patch for 1.35 or just will be just released in the next version of boost? Will you please specify which file was fixed so that I can download myself and rebuild? thanks Marc ----- Original Message ---- From: Gennadiy Rozental <rogeeff(a)gmail.com> To: boost-users(a)lists.boost.org Sent: Thursday, July 17, 2008 11:18:13 PM Subject: Re: [Boost-users] run_test parameter not working (Boost Unit Test Framework) Marc Oliver Castañeda <floranteatlaura <at> yahoo.com> writes: > > > Hi,I've downloaded the 1.35.0 source and built my own boost > libraries in Redhat 5.1 withthe intention of using the boost > unit test framework. However, I noticed that the run_test > parameter is not working.Has anyone experienced this and > came up I believe this is fixed in svn. Therer was incorrect ifdef that disabled the functionality on most platforms. Gennadiy _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

4 6

Multiple "serialize" functions
by John Krajewski 28 Jul '08

28 Jul '08

Newbie question for the boost serialization library.. In my app I want to have two seperate serialization modes: One when I'm saving all the data, and one when I'm creating a 'save game'. The two will be an overlapping set of parameters. Is there a good way to do this with the serialization library? Some way to specify seperate functions to call. I'm about to add a global flag that I can check in my single serialize function, and then check that to determine if I'm saving data or a save game, but this is a bit of a hack and I'd rather have a seperate function. Many thanks John Krajewski

2 1

Boost::ProgramOptions configuration files: an unusual request
by HTT-Bird 28 Jul '08

28 Jul '08

Alright, my problem is that in my configuration file, I need to carry data that maps names to a set of permissions (represented as strings when in the file, of course). There are two basic solutions that I can think of: the one-line-per-name approach and the entire-mapping-in-one-configuration-line approach. Is it possible to do the former with ProgramOptions and if so, how? Also, what would be a good syntax for the latter?

2 1

Cross compile Boost on Debian
by Joost Kraaijeveld 28 Jul '08

28 Jul '08

Hi, I would like to compile the Boost Libraries using the Debian MingW cross compiler. Is that possible, and if so, how should I do that? I have tried several configure and bjam options but they did not succeed. I also tried to compile everything on Windows and copy the files to my Debian machine, but for some unknown reason the regex library does not compile into a dll and I cannot get the static library to link: it gives me errors on " undefined reference to `__Unwind_Resume'" TIA -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl

1 0

Re: [Boost-users] noman javed: " problem in returning mpl::list"
by noman javed 28 Jul '08

28 Jul '08

I have already tried this and got the following error messeges example.cpp: In instantiation of ‘Poplist::apply<boost::mpl::list_c<int, 0l, 1l, 2l, 3l, 4l, 5l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l> >’: example.cpp:51: instantiated from here example.cpp:20: error: invalid use of undefined type ‘struct boost::mpl::pop_front<boost::mpl::list_c<int, 0l, 1l, 2l, 3l, 4l, 5l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l> >’ ../boost_1_35_0/boost/mpl/pop_front_fwd.hpp:20: error: declaration of ‘struct boost::mpl::pop_front<boost::mpl::list_c<int, 0l, 1l, 2l, 3l, 4l, 5l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l, 2147483647l> >’

3 2

problem in returning mpl::list
by noman javed 28 Jul '08

28 Jul '08

Hi I am trying to write a meta-function class, receiving a list as argument and returning the reduced list by poping one element from the front. Here is my code struct Poplist { template<class seq> struct apply { typedef pop_front<seq>::type res; static const int value = size<seq>::value; }; }; int main() { typedef list_c<int,0,1,2,3,4,5> numbers; cout<<Poplist::apply<numbers>::value<<endl; } And I got the following error example.cpp:20: error: type ‘boost::mpl::pop_front<seq>’ is not derived from type ‘Poplist::apply<seq>’ example.cpp:20: error: expected ‘;’ before ‘res’ Can someone please rectify my code Thanks in advance

3 2

Is there a something in boost to facilitate binary buffer transformations into typed data structures/classes?
by Graham Reitz 28 Jul '08

28 Jul '08

I didn't see anything, but I may have missed something. Problem: Binary data is stored in a char buffer from a proprietary device: char* buffer = new char[6]; Data in buffer: [byte 1][byte 2][byte 3][byte 4][byte 5][byte 6] [---16 bit uint--][------------32 bit uint-------------] ...would like to convert to this in a C++'ish style using a boost facility if it exists: (or consider directing me somewhere else if it doesn't) struct // or class { boost::uint16_t first; boost::uint32_t second; } data; I would like to avoid a C-style way of doing this. This seems like something that would have been solved many times. thanks, graham

4 8

Re: [Boost-users] XML library?
by Tan, Tom (Shanghai) 28 Jul '08

28 Jul '08

> On Sat, Jul 26, 2008 at 03:44:54PM +0200, Michiel Helvensteijn wrote: > > In the meantime, can anyone recommend another open source C++ XML library I > can use (with DOM parser)? > >http://xerces.apache.org/xerces-c/ POCO: http://www.appinf.com/poco/info/index.html

1 0

German language Boost tutorial available
by Ruediger Berlich 27 Jul '08

27 Jul '08

Hi there, by the beginning of this year I have written a three-part tutorial on using Boost for a German IT publication ("iX"). The magazine has now made the articles publicly available on their web page, under the following URLs: http://www.heise.de/ix/artikel/2007/12/134/ http://www.heise.de/ix/artikel/2008/01/144/ http://www.heise.de/ix/artikel/2008/02/138/ Note that the articles still refer to Boost 1.33.x/1.34, so that a few things are not applicable anymore to the upcoming version 1.36 . Hopefully they are nevertheless usefull for a few people. Best Regards, Ruediger /*************************************************************************/ The Steinbuch Centre for Computing of Karlsruhe Institute of Technology (the Cooperation of Forschungszentrum Karlsruhe GmbH and Universitaet Karlsruhe TH) will run its annual GridKa School from September 8th to 12th, 2008. Please find further information at http://www.fzk.de/gks08 . /*************************************************************************/

2 1

[Boost.thread] Exception handling strategy ?
by Ruediger Berlich 27 Jul '08

27 Jul '08

Hi there, is there a recommended strategy for exception (or more generally error-)handling with Boost.thread ? From what I can see it is not safe to throw an exception from within a thread, as it is not sure who catches it (or whether it gets caught at all). Best, Ruediger

7 13

[ASIO] Correct way to reconnect a failed TCP connection
by Simon Pickles 27 Jul '08

27 Jul '08

Hello, I am having a little trouble getting my boost::ASIO TCP client to actually re-attempt a connected if the first attempt failed. With my server offline, the call to async_connect correctly times out. When I try the async_connect call a second time, it doesn't time out. I am running my io_service listener in a boost thread, and am not changing this between async_connect calls. However, my debugger (MSVC2005, boost 1.35) does show a thread exit at this time. I don't think its the relevant thread (at the second call to connect there is an extra thread running (the io_service I guess). Here's my two relevant files. Thanks very much for any pointers Simon // Network.cpp //-------------------- // CNetwork::Connect // ........ m_client = boost::shared_ptr<CASIOClient>( new CASIOClient( m_log, m_initXML, m_IO, this ) ); try { tcp::resolver resolver(*(m_IO.get())); tcp::resolver::query query( m_serverHost.c_str(), m_serverPort.c_str() ); tcp::resolver::iterator iterator = resolver.resolve(query); m_client->Connect(iterator); m_log->NET( "Looking for Server at %s:%s\n", m_serverHost.c_str(), m_serverPort.c_str() ); } catch (boost::system::error_code& e) { m_log->NET("%s\n", e.message().c_str() ); m_log->NET("Server not found?\n"); return -1; } catch (std::exception& e) { m_log->NET("Exception %s\n", e.what() ); return false; } // start the io service to listen for async ops if ( !m_listener ) m_listener = boost::shared_ptr<boost::thread>( new boost::thread(boost::bind(&boost::asio::io_service::run, m_IO.get()) ) ); //------------------------------------- // CASIOClient.cpp CASIOClient::CASIOClient( boost::shared_ptr<ILogInterface> log, boost::shared_ptr<IXMLInterface> xml, boost::shared_ptr<boost::asio::io_service> io, CNetwork* network ): m_IO(io), m_socket(*(io.get())), m_network(network) { m_log = log; m_initXML = xml; } void CASIOClient::Connect( tcp::resolver::iterator endpoint_iterator ) { tcp::endpoint endpoint = *endpoint_iterator; m_socket.async_connect( endpoint, boost::bind( &CASIOClient::HandleConnect, this, boost::asio::placeholders::error, ++endpoint_iterator)); m_connectionState = NETWORK_DISCONNECTED; } void CASIOClient::Close() { m_log->NET("Starting Close...\n"); m_IO->post(boost::bind(&CASIOClient::DoClose, this)); } ////////////////////////////////////////// void CASIOClient::HandleConnect( const boost::system::error_code& error, tcp::resolver::iterator endpoint_iterator) { if (!error) { m_log->NET("Connected: %s\n", error.message().c_str()); m_connectionState = NETWORK_CONNECTED; boost::asio::async_read_until( m_socket, m_rx, '@', // termination char boost::bind( &CASIOClient::HandleReadUntil, this, boost::asio::placeholders::error)); } else if (endpoint_iterator != tcp::resolver::iterator()) { m_log->NET("Connection unsuccessful: %s\n", error.message().c_str()); m_log->NET("Retrying\n"); tcp::endpoint endpoint = *endpoint_iterator; m_socket.async_connect( endpoint, boost::bind( &CASIOClient::HandleConnect, this, boost::asio::placeholders::error, ++endpoint_iterator)); } else { m_log->NET("Connect Error: %s\n", error.message().c_str()); DoClose(); } } void CASIOClient::HandleReadUntil(const boost::system::error_code& error) { if (!error) { std::istreambuf_iterator<char> iter(&m_rx); std::istreambuf_iterator<char> end; std::string read(iter, end); std::string clipMsg; while (read.length()) { int n = read.find("@"); clipMsg = read.substr( 0, n ); m_log->NET( "Message received: %s\n", clipMsg.c_str() ); m_network->QueueReceivedMessage( clipMsg ); read = read.substr( n+1, read.length()-n-1 ); } // start listening again boost::asio::async_read_until( m_socket, m_rx, '@', boost::bind( &CASIOClient::HandleReadUntil, this, boost::asio::placeholders::error)); } else { m_log->NET( "ReadUntil Error: %s\n", error.message().c_str() ); DoClose(); } } void CASIOClient::DoClose() { m_log->NET( "Closing ASIO\n" ); m_socket.close(); m_connectionState = NETWORK_FAILED; }

2 1

[boost-users][StateChart] failure during termination
by Igor R 27 Jul '08

27 Jul '08

Hello, When trying to terminate an asynchronous_state_machine I get the error message: "Expression: list iterator not decrementable". This occures in state_machine::terminate_impl( state_base_type & theState, bool performFullExit ) in the line: else if ( currentStates_.begin() == --currentStatesEnd_ ), when trying to perform --currentStatesEnd_, as currentStatesEnd_== 0xcdcdcdcd (i.e. uninitialized). theState == outermost state of the machine. I believe the problem is actually somewhere in my own code, so my question is what it could be, according to the above symptom? I request the termination in the following way: struct ServerImpl { //.... shared_ptr<state_chart::fifo_scheduler<> > sessionScheduler_; state_chart::fifo_scheduler<>::processor_handle sessionProcessor_; ~ServerImpl() { // the scheduler resides in some pool, so it continues living after ~ServerImpl sessionScheduler_->terminate_processor(sessionProcessor_); } Thank you, Igor'.

1 1

[Graph] Disjoint Sets and Incremental Components with VertexList=listS
by Pedro Teixeira 27 Jul '08

27 Jul '08

Hi all, I am quite new to boost and would appreciate a hint on the following matter. My doubt is related to what exactly does the API expects in terms of a ReadWriteProperty and currently I am not amble to figure it out how to instantiate a disjoint_set for a graph of type adjacency_list <setS, listS, undirectedS>. The example (to a vecS graph) shows: std::vector<size_type> rank(num_vertices(G)); std::vector<Vertex> parent(num_vertices(G)); typedef size_type* Rank; typedef Vertex* Parent; disjoint_sets<Rank, Parent> ds(&rank[0], &parent[0]); I just spent some time trying different combinations of map<Vertex, size_type> and map<Vertex, Vertex> but it does not work. Also tried boost::property_map<Graph, boost::vertex_predecessor_t>::type for parent, but it didn't work either. Can anyone shed some light? thanks! Pedro

1 0

How do I push_back classes that disallow copy construction?
by Kevin Jenkins 26 Jul '08

26 Jul '08

How do I do this? Is there a way to make the boost::fusion vector hold references instead of copies? Or hold pointers? class DoNotCopyConstructMe { public: DoNotCopyConstructMe() {} private: DoNotCopyConstructMe(const DoNotCopyConstructMe &ref) {} }; DoNotCopyConstructMe var1,var2,var3,var4; boost::fusion::push_back(boost::fusion::make_vector(var1,var2,var3),var4); Error 1 error C2248: 'DoNotCopyConstructMe::DoNotCopyConstructMe' : cannot access private member declared in class 'DoNotCopyConstructMe' c:\boost_1_35_0\boost\fusion\view\single_view\single_view.hpp 38

2 1

Re: [Boost-users] XML library?
by Andrej van der Zee 26 Jul '08

26 Jul '08

I would definitely prefer libxml2/libxml++ over xerces-c (its too big and awkward in usage - prepare to type alot). For simple and basic usage you could also use tinyxml/ticpp or rapidxml. And yes, its a pitty that Boost does not provide some basic XML parser/generator. In so many projects you end up needing just a simpel parser... Cheers, Andrej ----- Original Message ---- From: Michiel Helvensteijn <m.helvensteijn(a)gmail.com> To: boost-users(a)lists.boost.org Sent: Saturday, 26 July, 2008 10:44:54 PM Subject: [Boost-users] XML library? I was surprised not to find an XML parser/generator library in boost. Or is it hidden somewhere? Is it planned for a future release, perhaps? In the meantime, can anyone recommend another open source C++ XML library I can use (with DOM parser)? Thanks! -- Michiel Helvensteijn _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

2 1

(A dynamic) Singleton using weak_ptr and shared_ptr
by Martin Trappel 26 Jul '08

26 Jul '08

Hi all. I was faced with the requirement for a singleton class where the object has to be constructed dynamically and where I wanted to assure that the object is destructed automatically when no longer needed. A solution using shared_ptr and weak_ptr immediately came to mind and after a short google I found http://lists.boost.org/boost-users/2002/10/2014.php. However, if you have to assure that construction and destruction never overlap if you have multiple (sequential) initializations/destructions it gets a bit more complicated :) Well. Here follows what I have come up with and it seems to work pretty well. Any comments welcome. br, Martin Singleton using boost weak_ptr and shared_ptr --------------------------------------------- Requirement: Singleton that is constructed on first use (not on process start) and destroyed after the last "client-code" has finished with it. Note: It is therefore possible that more that one Singleton instances exist within a process's lifetime, BUT there must only be at most one Object active at any given time (Construction must not run before destruction has finished. Starting point: http://lists.boost.org/boost-users/2002/10/2014.php Problem of the simple solution: No protection against multiple initialization and against simultaneous deletion and construction. Solution: The construction and destruction of the singleton instance(s) has to be protected additionally. [CODE:dynamic_singleton.h] #pragma once ////////////////////////////////////////////////////////////////////// #include <boost/noncopyable.hpp> #include <boost/shared_ptr.hpp> #include <boost/scoped_ptr.hpp> ////////////////////////////////////////////////////////////////////// class dynamic_singleton : private boost::noncopyable { public: typedef boost::shared_ptr<dynamic_singleton> shared_t; static shared_t get_instance(); // Interface: void example(int cookie); // ... private: dynamic_singleton(); virtual ~dynamic_singleton(); struct impl; typedef boost::scoped_ptr<impl> impl_t; impl_t pimpl; struct deleter; friend struct deleter; }; [/CODE] [CODE:dynamic_singleton.cpp] #include "dynamic_singleton.h" #include <boost/weak_ptr.hpp> #include <boost/thread/recursive_mutex.hpp> #include <boost/thread.hpp> ////////////////////////////////////////////////////////////////////// #define MESG(msg) \ printf("%s\n", msg); \ /**/ ////////////////////////////////////////////////////////////////////// class atomic_bool : protected boost::noncopyable { public: atomic_bool() : b_(false) {} explicit atomic_bool(bool b) : b_(b) {} inline operator bool() const { boost::recursive_mutex::scoped_lock lock(sync_); return b_; } inline bool operator=(bool b) { boost::recursive_mutex::scoped_lock lock(sync_); b_ = b; return b_; } private: bool b_; mutable boost::recursive_mutex sync_; }; ////////////////////////////////////////////////////////////////////// struct dynamic_singleton::impl : private boost::noncopyable { impl() {} ~impl() {} static void start_construction() { boost::xtime spin_time; spin_time.sec = 1; while(the_object_exists) { boost::thread::sleep(spin_time); } } static void finish_construction() { assert(!the_object_exists); the_object_exists = true; } static void finish_destruction() { assert(the_object_exists); the_object_exists = false; } typedef boost::weak_ptr<dynamic_singleton> internal_shared_t; static internal_shared_t the_object; static boost::recursive_mutex sync_init; static atomic_bool the_object_exists; }; ////////////////////////////////////////////////////////////////////// dynamic_singleton::impl::internal_shared_t dynamic_singleton::impl::the_object; boost::recursive_mutex dynamic_singleton::impl::sync_init; atomic_bool dynamic_singleton::impl::the_object_exists; ////////////////////////////////////////////////////////////////////// struct dynamic_singleton::deleter { void operator() (dynamic_singleton* p) { assert(p); delete p; impl::finish_destruction(); } }; ////////////////////////////////////////////////////////////////////// dynamic_singleton::shared_t dynamic_singleton::get_instance() { // Syncronise Initialization: boost::recursive_mutex::scoped_lock lock(impl::sync_init); MESG(__FUNCTION__); // Acquire singleton pointer: shared_t object_ptr = impl::the_object.lock(); if(!object_ptr.use_count()) { impl::start_construction(); object_ptr.reset(new dynamic_singleton(), dynamic_singleton::deleter()); impl::the_object = object_ptr; impl::finish_construction(); } return object_ptr; } ////////////////////////////////////////////////////////////////////// dynamic_singleton::dynamic_singleton() { pimpl.reset(new impl()); MESG(__FUNCTION__); // For example open a unique system or process global resource printf(" >> Singleton opens the global resouce.\n"); } ////////////////////////////////////////////////////////////////////// dynamic_singleton::~dynamic_singleton() { MESG(__FUNCTION__); // For example close a unique system or process global resource printf(" << Singleton closes the global resouce.\n"); } ////////////////////////////////////////////////////////////////////// void dynamic_singleton::example(int cookie) { printf("%s(%d)\n", __FUNCTION__, cookie); } [/CODE] [CODE:main.cpp] #include "dynamic_singleton.h" #include <iostream> #include <boost/thread.hpp> struct singleton_user { explicit singleton_user(int num) : num_(num) { } void operator()() { using namespace std; printf("%d uses singleton ...\n", num_); dynamic_singleton::shared_t s = dynamic_singleton::get_instance(); s->example(num_); } int num_; }; int main(int argc, char* argv[]) { boost::thread t1( singleton_user(1) ); boost::thread t2( singleton_user(2) ); boost::thread t3( singleton_user(3) ); boost::thread t4( singleton_user(4) ); boost::thread t5( singleton_user(5) ); t1.join(); t2.join(); t3.join(); t4.join(); t5.join(); return 0; } [/CODE]

3 2

[interprocess]Named mutex question
by Eugen Stoianovici 26 Jul '08

26 Jul '08

Is there a way to free a mutex which was locked by a process that died? I'm using a named mutex to synchronize access for some processes on a windows machine. One of those processes died while holding the mutex and now i can't get access to it (not even after killing every process that had any access to it). Is there a way to handle this situation through code?

2 6

Re: [Boost-users] Boost.Date_Time - How to measure time elapsed?
by Tan, Tom (Shanghai) 26 Jul '08

26 Jul '08

>I've been struggling with how to use the Date_Time library to measure >time elapsed (like to measure how long code takes to execute). >Could somebody provide me with an example? Resolution should be around >msec. I could not find any in the reference that particularly >addresses this. I would suggest using boost::timer instead. It's quite simple: #include <boost/timer.hpp> boost::timer t; // code to be measured.... Double e = t.elapsed(); t.restart(); // code to be measured.... e = t.elapsed();

7 8

MPL and Fusion ADL problem
by Joel FALCOU 26 Jul '08

26 Jul '08

Hi, I wanted to know how large can be the "fixing" of MPL/Fusion ADL for function and/or meta-function with somehow common name (length,size etc) ? Not sure if I am alone but I feel clumsy to "hide" fusion types from template argument list just so my own size() function don't conflicts with boost one. Considering the task, if it' sdoable but long, I can help by doing some of it myself. Of course, if there is smarter way to do so, let me know :) Thanks in advance -- Joel FALCOU Research Engineer @ Institut d'Electronique Fondamentale Université PARIS SUD XI France

2 1

[Serialization, Signals?] Memory leaks while deserializing derived type
by Brad Anderson 26 Jul '08

26 Jul '08

I'm getting memory leaks when deserializing objects and I can't figure out what I'm doing wrong. I'm using VC++ 2005. I've boiled it down to the following code: #include <fstream> // include headers that implement a archive in simple text format #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/vector.hpp> #include <boost/serialization/shared_ptr.hpp> #include <boost/shared_ptr.hpp> #include <boost/signal.hpp> // memory leak detection #ifdef _MSC_VER # include <valarray> // doesn't like the free() replacement macro # define _CRTDBG_MAP_ALLOC # include <stdlib.h> # include <crtdbg.h> #endif using boost::signal; class Base : public boost::enable_shared_from_this<Base> { public: typedef boost::shared_ptr<Base> sptr; //virtual ~Base() { } // uncommmenting this causes leaks to disappear private: virtual int virt() = 0; // commenting this line causes leaks to disappear friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { } }; class Derived : public Base { private: int virt() { return 0; } friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & boost::serialization::base_object<Base>(*this); } signal<void (int, const Base::sptr&)> m_derivedSignal1; }; int main(int argc, const char* argv[]) { #ifdef _MSC_VER _CrtSetDbgFlag ( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF ); #endif { Base::sptr loose_derived(new Derived()); } // no leak // create and open a character archive for output std::ofstream ofs("temp_serialize_file"); Base::sptr d_instance(new Derived()); // no leak std::vector<Base::sptr> d_list; d_list.push_back(d_instance); // save data to archive { boost::archive::text_oarchive oa(ofs); oa.register_type<Derived>(); // write class instance to archive oa & d_list; // archive and stream closed when destructors are called } // load data from archive std::vector<Base::sptr> loaded_d; { std::ifstream ifs("temp_serialize_file", std::ios::binary); boost::archive::text_iarchive ia(ifs); ia.register_type<Derived>(); // read class state from archive ia & loaded_d; // archive and stream closed when destructors are called // loaded instance has leak in memory allocated in boost signals } return 0; } Any ideas would be very appreciated. Brad Anderson

3 4

bundled graph property access?
by Jeffrey Trull 26 Jul '08

26 Jul '08

Hi all, I've found very few references to the use of bundled properties for graph properties, as opposed to edge and vertex properties. Are these supported? I find that I can supply a bundled property type name for the adjacency_list constructor, but cannot use "get_property" to access individual field values. This type of syntax works: adjlist.m_property.fieldname = whatever; but this does not: get_property(adjlist, &graphproptype::fieldname) = whatever; although it seems like the second form would be proper (for data hiding, and also the documentation suggests this is right - at least for old-style internal properties). To be specific, the following code does not compile: // test case for bundled graph properties #include <boost/graph/adjacency_list.hpp> #include <iostream> using namespace std; using namespace boost; /// circuit graph vertex properties struct VertexProps { }; /// circuit graph edge props struct EdgeProps { }; /// graph properties struct GraphProps { int blah; }; typedef adjacency_list<vecS, // storage for vertices vecS, // storage for edges directedS, // edges are directed VertexProps, EdgeProps, GraphProps> TestGraph; int main(int argc, char **argv) { TestGraph mygraph; set_property(mygraph, &GraphProps::blah, 1); } /usr/include/boost/graph/adjacency_list.hpp: In function void boost::set_property(boost::adjacency_list<OutEdgeListS, VertexListS, DirectedS, VertexProperty, EdgeProperty, GraphProperty, EdgeListS>&, Tag, const Value&) [with OEL = boost::vecS, VL = boost::vecS, DirS = boost::directedS, VP = VertexProps, EP = EdgeProps, GP = GraphProps, EL = boost::listS, Tag = int GraphProps::*, Value = int]: test_graphprops.cpp:29: instantiated from here /usr/include/boost/graph/adjacency_list.hpp:433: error: no matching function for call to get_property_value(GraphProps&, int GraphProps::*) Any suggestions? Thanks and Regards, Jeff Trull

1 0

Problem including boost/shared_ptr.hpp
by Marcelo Tomim 25 Jul '08

25 Jul '08

Hello Everyone, I have been trying to include boost/shared_ptr.hpp in a project I am working on, but the compiler keeps giving me the following errors: /usr/include/boost/shared_ptr.hpp:341: error: expected unqualified-id before string constant /usr/include/boost/shared_ptr.hpp:346: error: expected unqualified-id before string constant /usr/include/boost/shared_ptr.hpp:352: error: expected unqualified-id before string constant /usr/include/boost/shared_ptr.hpp:357: error: expected unqualified-id before string constant /usr/include/boost/shared_ptr.hpp:362: error: expected unqualified-id before string constant However, the most mind-boggling part is that if I include the same header file in a program by itself (i.e., outside my project) it compiles fine. Can anybody help me? I really appreciate any suggestion. Regards, Marcelo Aroca Tomim

3 2

Re: [Boost-users] Asio - Errors (Igor R)
by Brian T Crowder 25 Jul '08

25 Jul '08

-----Original Message----- From: Igor R <boost.lists(a)gmail.com> Sent: Friday, July 25, 2008 10:20 AM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Asio - Errors (Igor R) > I guess this means the socket itself is invalid but if i put the local end > point into the constructor for the socket_ as below it works fine. > > socket_(io_service, udp::endpoint( udp::v4(), port ) ) According to the ASIO reference: http://www.boost.org/doc/libs/1_35_0/doc/html/boost_asio/reference/basic_da… "This constructor creates a datagram socket and automatically opens it bound to the specified endpoint on the local machine. " In your example, the socket was created but it's not "open" yet, (so it doesn't have a valid handle). So before you bind() it, you have to open() it: http://www.boost.org/doc/libs/1_35_0/doc/html/boost_asio/reference/basic_da… _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] Asio - Errors (Igor R)
by Tim Pynegar 25 Jul '08

25 Jul '08

Hi, This is the code i'm trying to run. server(boost::asio::io_service& io_service, short port) : io_service_(io_service), socket_(io_service) { try { udp::endpoint localEndpoint( udp::v4(), port ); socket_.bind( localEndpoint ); } catch( boost::system::system_error & error ) { std::cerr << "Exception: " << error.what() << "\n"; } socket_.async_receive_from( boost::asio::buffer(data_, max_length), sender_endpoint_, boost::bind(&server::handle_receive_from, this, boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred) ); } and the error i get is "The file handle supplied is not valid" I guess this means the socket itself is invalid but if i put the local end point into the constructor for the socket_ as below it works fine. socket_(io_service, udp::endpoint( udp::v4(), port ) ) Thanks, Tim. > What message and the code of the system_error you've got? Probably, it > will explain the reason of the error. > By the way, most of the asio functions have no-throw version that gets > error_code& as a paramter and fills it in case of error. > >

2 1

[Boost Graph Library] Problem with a simple undirected_dfs example
by Ashwin N 25 Jul '08

25 Jul '08

Hi, I'm trying to get a simple undirected_dfs example to work. The aim is simple, to create an undirected graph and print its nodes in DFS order. Here's my code: ///////////////////////////////////////////////////////////////////////////////////// #include <boost/graph/adjacency_list.hpp> #include <boost/graph/undirected_dfs.hpp> #include <iostream> using namespace std; typedef boost::adjacency_list<boost::listS, boost::vecS, boost::undirectedS> MyGraph; typedef boost::graph_traits<MyGraph>::vertex_descriptor MyVertex; typedef boost::graph_traits<MyGraph>::edge_descriptor MyEdge; class MyVisitor : public boost::default_dfs_visitor { public: void discover_vertex(MyVertex v, const MyGraph& g) const { cerr << v << endl; } }; int main() { MyGraph g; boost::add_edge(0, 1, g); boost::add_edge(0, 2, g); boost::add_edge(1, 3, g); MyVisitor vis; boost::undirected_dfs(g, boost::visitor(vis)); return 0; } ///////////////////////////////////////////////////////////////////////////////////// I get the following errors which just make no sense to me: ///////////////////////////////////////////////////////////////////////////////////// Error 1 error C2780: 'void boost::put(T Bundle::* ,boost::adjacency_list<OutEdgeListS,VertexListS,DirectedS,VertexProperty,EdgeProperty,GraphProperty,EdgeListS> &,const Key &,const T &)' : expects 4 arguments - 3 provided d:\boost\boost\graph\undirected_dfs.hpp 149 Error 2 error C2780: 'void boost::put(Property,boost::adj_list_helper<Config,Base> &,const Key &,const Value &)' : expects 4 arguments - 3 provided d:\boost\boost\graph\undirected_dfs.hpp 149 Error 3 error C2784: 'void boost::put(const boost::put_get_helper<Reference,PropertyMap> &,K,const V &)' : could not deduce template argument for 'const boost::put_get_helper<Reference,PropertyMap> &' from 'boost::detail::error_property_not_found' d:\boost\boost\graph\undirected_dfs.hpp 149 Error 4 error C2784: 'void boost::put(const boost::writable_property_map_archetype<KeyArchetype,ValueArchetype> &,const writable_property_map_archetype<KeyArchetype,ValueArchetype>::key_type &,const writable_property_map_archetype<KeyArchetype,ValueArchetype>::value_type &)' : could not deduce template argument for 'const boost::writable_property_map_archetype<KeyArchetype,ValueArchetype> &' from 'boost::detail::error_property_not_found' d:\boost\boost\graph\undirected_dfs.hpp 149 Error 5 error C2784: 'void put(T *,ptrdiff_t,const V &)' : could not deduce template argument for 'T *' from 'boost::detail::error_property_not_found' d:\boost\boost\graph\undirected_dfs.hpp 149 ///////////////////////////////////////////////////////////////////////////////////// What am I doing wrong? How do I get to print nodes in DFS order? I'm on VC++ 2008 Express Edition. I have looked at the undirected_dfs example given here: <http://www.boost.org/doc/libs/1_35_0/libs/graph/example/undirected_dfs.cpp> That code seems to be trying to achieve something else. TIA, ~ash -- Groucho Marx - "A hospital bed is a parked taxi with the meter running."

2 1

[interprocess]managed memory segment items
by Eugen Stoianovici 25 Jul '08

25 Jul '08

Is there a way to get all names for objects mapped into a managed shared memory? Thanks, Eugen -- Sent from Gmail for mobile | mobile.google.com

2 1

Asio - Errors
by Tim Pynegar 25 Jul '08

25 Jul '08

Hi, I'm trying to call bind on a udp::socket separately from the udp::socket constructor. As in when i use the overloaded udp::socket constructor and pass in a local endpoint for it to do the bind on it work's fine. However when i only pass in the boost::asio::io_service and then call bind on the socket later with a local scope udp::endpoint it throws the following exception. First-chance exception at 0x76b442eb in Chatter.exe: Microsoft C++ exception: boost::system::system_error at memory location 0x0012e774.. I've got two questions, the first is does anyone have any idea of what this is, and the second is how do i get access to the socket error codes or states. As in if i knew what the error was i'd maybe be able to fix this myself and i appriciate that it's difficult without seeing the code itself to tell me what i'm doing wrong. Thanks, Tim.

3 2

Pool allocator with multiple dynamic libraries
by Fedor Chelnokov 25 Jul '08

25 Jul '08

Am I right in saying that when boost::pool_allocator is used in a Windows program consisting of several DLLs, there is no single shared pool but as many pools as the number of modules? So the usage of containers with boost::pool_allocator is not safe because of the allocator’s comparison operation (==), which is always returns true.

1 0

[test] BOOST_CHECK_EQUAL type to stream
by Michiel Helvensteijn 25 Jul '08

25 Jul '08

I understand why the types of the arguments to BOOST_CHECK_EQUAL (and BOOST_CHECK_PREDICATE, etc.) must have operator<< correctly defined. Otherwise, the failure message could not be properly printed. The type I want to check is vector<int>. But it seems not to be enough to simply define the following function: ostream& operator<<(ostream& out, const vector<int>& vec); The error message is long and very templatey, but the essence is: .../test_tools.hpp:298: error: no match for 'operator<<' in 'ostr << t' What more should I do to be able to use vector<int> in these tests? Thanks! -- Michiel Helvensteijn

6 25

using boost::test to test private methods
by david.weber＠l-3com.com 24 Jul '08

24 Jul '08

I've searched a little bit, but having some difficulties finding good examples. So, I have a template class, in which I'm trying to test some private methods. Let's table the philosophical reasons for doing so, I'm just having difficulties setting up the mechanics of it. The best way I've seen, is to make a testing class a friend of class to be tested. My class to be tested is in a namespace, that the test cases are not members of. I'm running into all sorts of compiler errors. Does anyone have sample code about making this work. Strategies for separating the test code from the production code as much as possible? This is a first stab at automatic unit testing for me, so any assistance would be great. Thanks --dw

2 1

[detail] atomic_count operator++ returns different types
by Doug Mahlum 24 Jul '08

24 Jul '08

Why does the atomic_count ++ operator return a "long" for the win32,solaris and sync compilers, but returns "void" for all gcc compilers? The -- operator returns a "long" in all cases, so this would appear to be an annoying, anomalous behavior. But hopefully a rational explanation exists. Also, if it's the value of the ++ that is wanted, two threads could return the same value of this atomic counter, since another call is required to obtain it for the gcc case. Thank you, Doug

1 0

the boost xml serialization to a stringstream does not have an end tag.
by Sangeeta Singh 24 Jul '08

24 Jul '08

Hi, When I xml serialize an object to a stringstream i get the following output <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!DOCTYPE boost_serialization> <boost_serialization signature="serialization::archive" version="3"> <bidResponse class_id="0" tracking_level="0" version="0"> <oppId>69</oppId> <delay>0</delay> <bid class_id="1" tracking_level="0" version="0"> <maxBid>5.3000002</maxBid> <minBid>5.3000002</minBid> <adBlob>adblob</adBlob> </bid> </bidResponse> As can be seen the end tag </boost_serialization> is missing. thi shappens even if I flush the stringstream. If i xml serialize to a text file I do not see this problem here is the o/p when I xml serialize to a text file <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!DOCTYPE boost_serialization> <boost_serialization signature="serialization::archive" version="3"> <bidRequest class_id="0" tracking_level="0" version="0"> <oppId>34567889</oppId> </bidRequest> <bidRequest class_id="0" tracking_level="0" version="0"> <oppId>44567889</oppId> </bidRequest> </boost_serialization> Any idea how to resolve this. Thanks, Sangeeta

5 5

Form Link
by anil kumar 24 Jul '08

24 Jul '08

Hi All, I have posted a mail regarding a problem and got a reply too and issue is also solved as i am new to this boost community can anybody tell me if there is any forum where we can easily post thread i mean any issue and sort it out because mailing the issue and waiting for the reply and my whole mail box is filled with lot of mails from the address. So can any one guide me where i can just log in and post issue and discuss with other BOOST users. Please send me the links to my mail id. Thanks in advance. Anil anil26_prodigy(a)hotmail.com _________________________________________________________________ Missed your favourite programme? Stop surfing TV channels and start planning your weekend TV viewing with our comprehensive TV Listing http://entertainment.in.msn.com/TV/TVListing.aspx

2 1

[numeric][conversion][docs] Questions about terms.
by John C. Femiani 24 Jul '08

24 Jul '08

I just read the docs for numeric/conversion at http://tinyurl.com/5bflvn, and I have some questions. Basically I am getting confused about abstract values versus represented values, verses how they are represented (e.g. as fixed point or floating point numbers). 1) Is the density of scaled integers or fixed point types greater than one? The size of the numeric set is larger than the width, so it seams like the density would be greater than one. 2) Is the precision of long int really greater than the precision of short int? It is strange to me that precision seems to have a different meaning for integer than for "floating" types. 3) What is the difference between the numeric sets "Whole" and "Int"? They both represent the same values from the set of integers, which is a subset of real numbers. Does this mean that the _way_ the values are represented is important? 4) Is it true that a fixed point type would be classified as a 'floating' type? Also, are complex types numeric? Thanks, --John

1 0

Re: [Boost-users] [boost-users][multi-index] passing modifier by reference/pointer?
by JOAQUIN M. LOPEZ MUÑOZ 24 Jul '08

24 Jul '08

________________________________________ De: boost-users-bounces(a)lists.boost.org [boost-users-bounces(a)lists.boost.org] En nombre de Igor R [boost.lists(a)gmail.com] Enviado el: miércoles, 23 de julio de 2008 19:53 Para: boost-users(a)lists.boost.org Asunto: [Boost-users] [boost-users][multi-index] passing modifier byreference/pointer? > > Hello, > > Is there a simple way to pass a modifier by reference/pointer in the > following expression: > > my_multi_index_container.modify(somePos, modifier); > > "modifier" is a functor that has some internal state, so I wouldn't > like it to be copied. > Is it possible to do this without an explicit creation of a binder > that binds operator() and &modifier (or so)? The following should do: modifier_type modifier(...); ... my_multi_index_container.modify<modifier_type&>(somePos, modifier); HTH, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

templating usage of state<>
by Tony Turner 24 Jul '08

24 Jul '08

Greetings; PROBLEM: I have a need to call a 'post_event' from the ctor of a templated state that belongs to a templated machine. BEST SHOT AT SOLUTION SO FAR: ( items #1,#2 & #3 below work fine... item #4, my goal, fails) Request for specific assistance is in item #5 below. Thank you for your time and effort, I know you are very busy and appreciate the help. Regards, Tony Turner acturner01(a)comcast.net //************************************************************************ (1) I started with the following non-templated version, which works just fine: ... namespace sc = boost::statechart; namespace mpl = boost::mpl; ... // fwd decl struct Start; struct Inst : public sc::state_machine< Inst, Start > {}; struct Start : public sc::state< Start, Inst > { Start(my_context ctx ) : my_base( ctx ) {// do some stuff ...} }; // 'main' routine is.... BOOST_AUTO_TEST_CASE(testMyMachine) { Inst myMachine; myMachine.initiate(); } //************************************************************************ (2) I then templated the machine, with no problems, which is half way to my solution: // fwd decl struct NDIREV_17 {}; struct Start; template< typename I > struct Inst : public sc::state_machine< Inst, Start > {}; struct Start : public sc::state< Start, Inst1<NDIREV_17> > { Start(my_context ctx ) : my_base( ctx ) {} }; // 'main' routine is.... BOOST_AUTO_TEST_CASE(testMyMachine) { Inst<NDIREV_17> myMachine; myMachine.initiate(); } //************************************************************************ (3) I then templated the simple_state<> version, which works just fine. struct NDIREV_17 {}; template< typename I > struct Start; template< typename I > struct Inst : public sc::state_machine< Inst, Start > {}; template< typename I > struct Start : public sc::simple_state< Start, Inst > { }; // same 'main' //************************************************************************ (4) finally, I templated the state<> version, , which has problems. [NOTE: I've referenced line # 3773 below, to sync with output] struct NDIREV_17 {}; template< typename I > struct Start; template< typename I > struct Inst : public sc::state_machine< Inst, Start > {};[ line# 3773 ] template< typename I > struct Start : public sc::state< Start, Inst > { Start(my_context ctx ) : my_base( ctx ) {} }; // same 'main' //************************************************************************ (5) ATTEMPTS TO FIX: a) look @ code in state.hpp ( shown below ) and attempt to replace "my_context" & "my_base" with direct substitutions of "simple_state" and this->set_context.... no luck. REQUEST FOR HELP: Could someone who has successfully templated both the machine<> and the state<> classes possibly give me a hint as to what I might be able to do to fix this bug? Thank you for your time and effort; Tony Turner acturner01(a)comcast.net //************************************************************************ (6) state.hpp fragment // here is 'state<> fragment from state.hpp template< class MostDerived, class Context, class InnerInitial = mpl::list<>, history_mode historyMode = has_no_history > class state : public simple_state< MostDerived, Context, InnerInitial, historyMode > { typedef simple_state< MostDerived, Context, InnerInitial, historyMode > base_type; protected: ////////////////////////////////////////////////////////////////////////// struct my_context { my_context( typename base_type::context_ptr_type pContext ) : pContext_( pContext ) { } typename base_type::context_ptr_type pContext_; }; typedef state my_base; state( my_context ctx ) { this->set_context( ctx.pContext_ ); } ~state() {} ------------------------------------------------------------ ------------------------------------------------------------ Resulting Error msg: Device.hpp:3774: error: expected `)' before 'ctx' In file included from src/bin/UnitTestDevice.cpp:25: Device.hpp:3774: error: expected `)' before 'ctx' /usr/include/boost/statechart/state.hpp: In static member function 'static typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::inner_context_ptr_type boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::shallow_construct(const typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::context_ptr_type&, typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]': /usr/include/boost/statechart/state.hpp:79: instantiated from 'static void boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::deep_construct(const typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::context_ptr_type&, typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]' /usr/include/boost/statechart/state.hpp:70: instantiated from 'static void boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::initial_deep_construct(typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]' /usr/include/boost/statechart/state_machine.hpp:701: instantiated from 'void boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initial_construct() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' /usr/include/boost/statechart/state_machine.hpp:716: instantiated from 'boost::statechart::result boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initial_construct_function::operator()() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' /usr/include/boost/statechart/null_exception_translator.hpp:33: instantiated from 'boost::statechart::result boost::statechart::null_exception_translator::operator()(Action, ExceptionEventHandler) [with Action = boost::statechart::state_machine<MNavAnts::Inst1<MNavAnts::NDIREV_99>, MNavAnts::Start1<MNavAnts::NDIREV_99>, std::allocator<void>, boost::statechart::null_exception_translator>::initial_construct_function, ExceptionEventHandler = boost::statechart::state_machine<MNavAnts::Inst1<MNavAnts::NDIREV_99>, MNavAnts::Start1<MNavAnts::NDIREV_99>, std::allocator<void>, boost::statechart::null_exception_translator>::exception_event_handler]' /usr/include/boost/statechart/state_machine.hpp:253: instantiated from 'void boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initiate() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' src/bin/UnitTestDevice.cpp:870: instantiated from here /usr/include/boost/statechart/state.hpp:89: error: no matching function for call to 'MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1( boost::statechart::state<MNavAnts::Start1<MNavAnts::NDIREV_99>, MNavAnts::Inst1<MNavAnts::NDIREV_99>, boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, has_no_history>::my_context)' Device.hpp:3773: note: candidates are: MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1() Device.hpp:3773: note: MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1(const MNavAnts::Start1<MNavAnts::NDIREV_99>&) /usr/include/boost/statechart/state.hpp: In static member function 'static typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::inner_context_ptr_type boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::shallow_construct(const typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::context_ptr_type&, typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]': /usr/include/boost/statechart/state.hpp:79: instantiated from 'static void boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::deep_construct(const typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::context_ptr_type&, typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]' /usr/include/boost/statechart/state.hpp:70: instantiated from 'static void boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::initial_deep_construct(typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]' /usr/include/boost/statechart/state_machine.hpp:701: instantiated from 'void boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initial_construct() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' /usr/include/boost/statechart/state_machine.hpp:716: instantiated from 'boost::statechart::result boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initial_construct_function::operator()() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' /usr/include/boost/statechart/null_exception_translator.hpp:33: instantiated from 'boost::statechart::result boost::statechart::null_exception_translator::operator()(Action, ExceptionEventHandler) [with Action = boost::statechart::state_machine<MNavAnts::Inst1<MNavAnts::NDIREV_99>, MNavAnts::Start1<MNavAnts::NDIREV_99>, std::allocator<void>, boost::statechart::null_exception_translator>::initial_construct_function, ExceptionEventHandler = boost::statechart::state_machine<MNavAnts::Inst1<MNavAnts::NDIREV_99>, MNavAnts::Start1<MNavAnts::NDIREV_99>, std::allocator<void>, boost::statechart::null_exception_translator>::exception_event_handler]' /usr/include/boost/statechart/state_machine.hpp:253: instantiated from 'void boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initiate() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' src/bin/UnitTestDevice.cpp:870: instantiated from here /usr/include/boost/statechart/state.hpp:89: error: no matching function for call to 'MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1( boost::statechart::state<MNavAnts::Start1<MNavAnts::NDIREV_99>, MNavAnts::Inst1<MNavAnts::NDIREV_99>, boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, has_no_history>::my_context)' Device.hpp:3773: note: candidates are: MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1() Device.hpp:3773: note: MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1(const MNavAnts::Start1<MNavAnts::NDIREV_99>&)

4 6

boost mutex 1.35.0 vs 1.34.0
by Vial, Florent 24 Jul '08

24 Jul '08

hi all, i was running happily with boost 1.34.0 under Win32, using boost::program_options, boost_filesystem, and boost::thread. i decided to update to 1.35.0. I had to fix some broken code (e.g. boost::filesystem::filesystem_error does not have a member system_error() anymore) which was ok. Tell me if I am wrong, but now if i want to use a tiny boost::mutex (#include <boost/thread/mutex.hpp>), not only have I to define WIN32_LEAN_AND_MEAN before the include to avoid cryptic error messages due to the inclusion of winsock.h though i am using winsock2.h, but also I must now link to boost_thread AND to boost_system ? is this right ? thank you for any useful insights, florent Arnold & Richter Cine Technik GmbH & Co. Betriebs KG Sitz: Munchen - Registergericht: Amtsgericht Munchen - Handelsregisternummer: HRA 57918 Personlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH Sitz: Munchen - Registergericht: Amtsgericht Munchen - Handelsregisternummer: HRB 54477 Geschaftsfuhrer: Prof. Dr. Dejan Ilic; Franz Kraus; Jens Schafer

2 1

Phoenix in 1.35.0
by Robert Jones 23 Jul '08

23 Jul '08

My understanding of the state of play with Phoenix is that the lovely Phoenix 2.0 is part of the not-yet-released Boost 1.36.0, and that the current release of Boost, 1.35.0 hosts Phoenix 1.2. Phoenix 2.0 has lovely documentation at http://spirit.sourceforge.net/dl_docs/phoenix-2/libs/spirit/phoenix/doc/htm… but the corresponding documentation for V1.2, at http://www.boost.org/doc/libs/1_35_0/libs/spirit/phoenix/index.html is buried inside the Spirit docs, and is not nearly as good as the v2.0 documentation. In particular the v1.2 docs are very quiet about specific include file paths, which have also changed significantly for v2.0. Is there anything I've missed in all this? ----------- Also looking through the documentation of Boost libraries in general, the quality varies widely. Am I correct in believing this is due to whether the various library authors have found time to write quality documentation? Regards, Rob. -- ACCU - Professionalism in programming - http://www.accu.org

2 1

[boost-users][multi-index] passing modifier by reference/pointer?
by Igor R 23 Jul '08

23 Jul '08

Hello, Is there a simple way to pass a modifier by reference/pointer in the following expression: my_multi_index_container.modify(somePos, modifier); "modifier" is a functor that has some internal state, so I wouldn't like it to be copied. Is it possible to do this without an explicit creation of a binder that binds operator() and &modifier (or so)? Thanks.

2 1

variant warnings?
by hfye-wila＠spamex.com 23 Jul '08

23 Jul '08

Does Boost.Variant require certain warnings to be disabled? The following program generates a warning for me with VC9: COMPILER INPUT: #include <boost/variant.hpp> #include <iostream> struct vis : public boost::static_visitor<> { void operator()( int & ) const { std::cout << "int" << std::endl; } void operator()( std::string & ) const { std::cout << "string" << std::endl; } }; int main( int, char * ) { boost::variant< int, std::string > v; boost::apply_visitor( vis(), v ); return 0; } COMPILER OUTPUT: 1>Compiling... 1>variant_basic.cpp 1>J:\work\ext\boost_ext\boost/variant/variant.hpp(894) : warning C4512: 'boost::detail::variant::invoke_visitor<Visitor>' : assignment operator could not be generated 1> with 1> [ 1> Visitor=const vis 1> ] 1> J:\work\ext\boost_ext\boost/variant/variant.hpp(1771) : see reference to class template instantiation 'boost::detail::variant::invoke_visitor<Visitor>' being compiled 1> with 1> [ 1> Visitor=const vis 1> ] 1> J:\work\ext\boost_ext\boost/variant/detail/apply_visitor_unary.hpp(72) : see reference to function template instantiation 'void boost::variant<T0_,T1>::apply_visitor<const Visitor>(Visitor &)' being compiled 1> with 1> [ 1> T0_=int, 1> T1=std::string, 1> Visitor=vis 1> ] 1> ..\indep\variant_basic.cpp(11) : see reference to function template instantiation 'void boost::apply_visitor<vis,boost::variant<T0_,T1>>(const Visitor &,Visitable &)' being compiled 1> with 1> [ 1> T0_=int, 1> T1=std::string, 1> Visitor=vis, 1> Visitable=boost::variant<int,std::string> 1> ]

2 5

[Test] Glue for Visual Studio automated unit testing
by Stephen Nuchia 23 Jul '08

23 Jul '08

Visual Studio 2008, in the pricier editions, has rich support for automated unit testing - of "managed" code units. Not much help with 4 million lines of native code! I've set up unit test projects within my overall solution. These build executables from source (using boost-test's default main() ) and run them using custom build step scripts. It's simple and it works but it does not tie into the test automation infrastructure. Test failures show up as build failures, and there's no direct support for things like test coverage analysis. It turns out, however, that if what you want to test has a COM or .NET interface, you can write a C# (or managed C++) test driver, reference the interface exported by the native code, and test away. But that doesn't help you unit test traditional libraries. What I'd like to do is to develop a .NET-visible wrapper for a boost-test unit test driver. This would allow us to author the actual tests in native C++ using boost-test, build and run the test suite as before if desired. We could, for instance, execute the test driver under the debugger to investigate a failure. But we could also drive the tests from a Visual Studio Test project. The simple thing to do would be to make each native test driver (with its entire suite of tests) one Studio-level test. It might be possible to expose the internal boost-test suite structure to the wrapper so the individual tests show up in the database; I'm not sure this is desirable and it would be more work. My main purpose in posting this note is to see if anybody out there is interested in working with me on this. Secondarily, I'd appreciate any advice from those more familiar with the guts of boost-test. What is the best place to hook in and what features does the exported interface (object model) need to expose? Because this effort targets special features found only in high-end versions of visual studio, it will not be of much interest to the majority of the readers of this list. I suggest folks send me email directly unless you think everyone needs to see it. -swn

3 2