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

synchronize threads from a thread pool (using asio::io_service)
by Daren Lee 05 Aug '11

05 Aug '11

Hi - I'm using asio::io_service as a dispatcher for a thread pool. I'm wondering how I can synchronize the threads after I post the tasks to the io_service. I tried using a barrier but it doesn't always work correctly. The barrier waits indefinitely; although I verified the post() function gets called, the io_service doesn't seem to dispatch anything. I've also thread using the boost::threadpool library but the overall speed is slower. I'd appreciate any insight on what I'm doing wrong with the barrier or any other high performance thread pooling alternatives. Thanks, Daren <code> void handler ( int i, int nSize, double *pArray, double *pTemp, boost::barrier *pBarrier ) { // compute on pArrray --> write result to pTemp[i] .... pBarrier->wait(); } double doCalc ( int nSize, double *pArray, double *pTemp ) { unsigned int nNumThreads = 8; int nSubSize = nSize / nNumThreads; boost::barrier barrier( nNumThreads + 1 ); for( int i=0;i<nNumThreads;i++ ) { if( i == nNumThreads-1 ) { m_io_service.post( boost::bind( &handler, i, nSize-(i*nSubSize), pArray+(i*nSubSize), pTemp, &barrier )); } else { m_io_service.post( boost::bind( &handler, i, nSubSize, pArray+(i*nSubSize), pTemp, &barrier )); } } barrier.wait(); // sum results double fSum = 0; for( int i=0;i<nNumThreads;i++ ) { fSum += pTemp[i]; } return fSum; } I initialize the io_service with work elsewhere as: boost::asio::io_service::work m_work( m_io_service ); boost::thread_group m_threads; for (std::size_t i = 0; i < m_nNumThreads; ++i) m_threads.create_thread(boost::bind(&boost::asio::io_service::run, &m_io_service)); </code>

1 0

What's wrong with this simple multithreaded function that uses regex?
by Andrew Yancy 05 Aug '11

05 Aug '11

The code snippet below is the core of a function mythreadfunc() that is run concurrently for several threads using the Win32 MSVC functions CreateThread() and WaitForMultipleObjects(). Everything seems to work fine except for actually using boost::regex_match(). For example, if that line below is changed to if(true), the entire multithreaded function works perfectly. Similarly, if mythreadfunc() as shown below is run without multiple threads, it works perfectly. But if mythreadfunc() as shown below is run with multiple threads, the entire program crashes with return value 0xc0000005, which is some kind of memory access violation. This leads me to believe that boost::regex does not play well with MSVC threads, but according to the Boost site, there aren't any bugs related to this issue for Boost 1.45. As far as I can tell I'm using Boost in thread safe mode (BOOST_HAS_THREADS is defined). I'm probably doing something really dumb related to MSVC threads or related to the way I configured Boost, but I'm not sure what it is! I could switch to using Boost threads, but I would like to minimize the changes to the code. Thanks very much for any help~ ... static const boost::regex expression("^[0-9]+"); ifstream myfile(x); //x is a different file name for every thread string line; if(myfile.is_open()) { while(myfile.good()) { getline(myfile, line); if(boost::regex_match(line, expression)) { //do stuff } } myfile.close(); } ...

5 7

[Filesystem] There must be a better way to do path decomposition
by Ramon F Herrera 04 Aug '11

04 Aug '11

This code at least works: string directory_path(argv[1]); path p(directory_path); ostringstream component; string lastComponent; for (path::iterator it = p.begin(); it != p.end(); it++) { component.str(""); // Hack, to be replaced by better way component << *it; // to grab `*it' in a string lastComponent = component.str(); } lastComponent = lastComponent.substr(1, lastComponent.size()-2); According to the documentation examples, the item pointed to by `*it' is of the following type: path::iterator::value_type is path::string_type, and iteration treats path as a container of filenames. I tried to capture `*it' in a string and in a string_type but the compiler does not like the '=' operator. TIA, -RFH

4 5

[iostreams] Unresolved external symbols gzip_footer::process etc.
by Clifford Cary 04 Aug '11

04 Aug '11

We recently upgraded from Boost 1.34.1 to 1.46.1 and moved from Visual Studio 2005 to VS 2010. We have an application that uses the Gzip decompression feature. The implementation includes these lines: Declaration: #include <boost/iostreams/device/file_descriptor.hpp> #include <boost/iostreams/filtering_stream.hpp> #include <boost/iostreams/device/file.hpp> #include <boost/iostreams/filter/gzip.hpp> boost::iostreams::filtering_streambuf<boost::iostreams::input> m_filter_stream; Executed code: m_filter_stream.push(io::gzip_decompressor()); m_filter_stream.push(m_file); m_input_stream = new istream(&m_filter_stream); m_input_stream->read((char*)m_buffer, BUFSIZE); The application linked without errors against the 1.34.1 library using VS 2005, but with 1.46.1 and VS 2010 we get four unresolved external symbols: public: void __cdecl boost::iostreams::detail::gzip_footer::process(char) public: void __cdecl boost::iostreams::detail::gzip_footer::reset(void) public: void __cdecl boost::iostreams::detail::gzip_header::process(char) public: void __cdecl boost::iostreams::detail::gzip_header::reset(void) The build is done on Windows XP x64 using the Boost 64-bit Windows binaries downloaded from http://boost.teeks99.com<http://boost.teeks99.com/>. The zlib binaries are also linked. Can someone suggest what the problem might be?

1 0

date _facet segmentation fault
by Kraus Philipp 04 Aug '11

04 Aug '11

Hello, I use this little code for formating a date value: std::stringstream l_stream; boost::gregorian::date_facet* l_format = new boost::gregorian::date_facet(); l_format->format("%Y-%m-%d"); l_stream.imbue(std::locale(std::locale::classic(), l_format)); If I call after the imbue a delete (delte l_format) to remove the date_facet from the heap the program creates a segmentation fault value. Does the std::stringstream remove the date_facet object from the heap? If not, how can I do a correct clear of the object? I hope, that question is not off topic. I would like to format a date value in a stringstream Thanks alot Phil

3 2

[test][1.47] Test cases segfault after completion
by Thomas Taylor 04 Aug '11

04 Aug '11

Hi! When compiling my test cases with 1.47 (no matter if dynamically or statically linked) they fail. Not the test cases themselves, but a segfault after the test case is done. The very same code compiled with r73480 executes as expected. HTH, Thomas Please find relevant valgrind output attached: Running 1 test case... *** No errors detected ==11042== Invalid write of size 8 ==11042== at 0x481152: execution_monitor_jumping_signal_handler (in /discs/rest/home/anubis/CPP/mdy- svn/gepetto/branches/build/g2_147/source/hoost/3d/test-unit__vec3d) ==11042== by 0x851380F: ??? (in /lib/libc-2.14.so) ==11042== by 0x85B3F44: shutdown (in /lib/libc-2.14.so) ==11042== by 0xC6FE47F: ??? (in /usr/lib/openmpi/openmpi/mca_oob_tcp.so) ==11042== by 0x78491EE: mca_oob_base_close (in /usr/lib/openmpi/libmpi.so.1.0.1) ==11042== by 0x788D61A: mca_base_components_close (in /usr/lib/openmpi/libmpi.so.1.0.1) ==11042== by 0x7861C09: orte_rml_base_close (in /usr/lib/openmpi/libmpi.so.1.0.1) ==11042== by 0x7831B69: orte_ess_base_app_finalize (in /usr/lib/openmpi/libmpi.so.1.0.1) ==11042== by 0xC4F579D: ??? (in /usr/lib/openmpi/openmpi/mca_ess_singleton.so) ==11042== by 0x7805067: orte_finalize (in /usr/lib/openmpi/libmpi.so.1.0.1) ==11042== by 0x77B1174: ??? (in /usr/lib/openmpi/libmpi.so.1.0.1) ==11042== by 0x70B4881: boost::mpi::environment::~environment() (in /usr/lib/libboost_mpi.so.1.47.0) ==11042== Address 0xa98 is not stack'd, malloc'd or (recently) free'd

2 2

Boost-log Formater with Syslog
by Shah, Gaurav N 04 Aug '11

04 Aug '11

Hi, I have any application running. I want to use boost.log for "syslog". How do I achive this? The log format I need is: <hostname> <LOGLEVEL> <appname> <timestamp> <threadid>message..... How to customize log format as above for syslog? Thanks for help in advance. _ Gaurav This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.

1 0

Disabling Tokenizer in Derived Classes - after their constructors have been executed.
by asif saeed 04 Aug '11

04 Aug '11

Hi, I have boost tokenizer and its iterator stored in my base class. The tokenizer got initialized with a const std::string&. I do the tokenization in my base class and provide the iterator, pointing to the first token, to the derived classes - but only to be used in their constructors. After the derived class constructor has been executed, the tokenizer and its iterator should not remain available - what can I do to accomplish that? Best regards, Asif

2 2

[network] Bagged, Tagged, New Release 0.9.1
by Dean Michael Berris 04 Aug '11

04 Aug '11

Good day everyone! If you're not interested in cpp-netlib's progress, please stop reading now. :) I'm happy to announce that cpp-netlib (the library that's hoping to be Boost.Network someday) is now available for general availability. You can get the latest from https://github.com/cpp-netlib/cpp-netlib/downloads and find out what's new at http://cpp-netlib.github.com/0.9.1/whats_new.html . This is an updated release that's inching closer to the "1.0" release that's going to be up for review. I've also written a more detail-filled announcement that you can read over at http://cplusplus-soup.com/2011/08/04/cpp-netlib-0-9-1-released/ -- please feel free to comment and share as you see fit. I'm looking to work with Michael Caisse who has agreed to be the review manager for Boost.Network to hopefully have a review at a convenient time for both of us. Right now I'm gunning for Q4 of 2011, but that's still fairly a ways away so things may still change. Cheers everyone, I do hope this helps! -- Dean Michael Berris http://about.me/deanberris

1 0

boost::thread - usage
by Christopher Pisz 03 Aug '11

03 Aug '11

I am trying to make a thread object, so I can later have better control of threads and the resources they are using. So, I started wrapping up a boost::thread. //----------------------------------------------------------------------------- ---------------------------------------------------------------- // BaseThread.h #include <boost/thread/thread.hpp> //----------------------------------------------------------------------------- - /// \brief Thread object that performs a task that is to run once (non- looped) /// \detail Derive from this class and implement the Work method to define the /// work this thread is to perform class BaseThread { public: BaseThread(); /// \brief Deconstructor /// \detail It is required that a derived class make a call to thread_.join() /// in its deconstructor virtual ~BaseThread(); virtual void Start(); virtual int Work() = 0; protected: void Run(); boost::thread thread_; }; //----------------------------------------------------------------------------- ---------------------------------------------------------------- // BaseThread.cpp #include "BaseThread.h" //----------------------------------------------------------------------------- - BaseThread::BaseThread() { } //----------------------------------------------------------------------------- - BaseThread::~BaseThread() { // Wait for the thread to complete thread_.join(); // DEBUG - Does join wait? int x = 1; } //----------------------------------------------------------------------------- - void BaseThread::Start() { boost::thread newThread(boost::bind(&BaseThread::Run, this)); thread_.swap(newThread); } //----------------------------------------------------------------------------- - void BaseThread::Run() { this->Work(); } I am kind of winging it here just going off of the boost documentation and guessing at what I should be doing. This code has a problem in that in order for us to wait for the thread to complete, the derived class is going to have to call thread_.join(). That leaves a bad taste in my mouth as I'd rather the base class take care of all the details, and all the derived class has to worry about is providing a Work method. This class doesn't provide much that boost::thread doesn't already have, but I want to make different classes for additonal requirements. One of which I have in mind is a thread with looped work and a start, stop, method. Making an object out of it will also probably help with derving classes that take care of locking their data...or at least organize it a bit. So the question 1 is, is there a way I can avoid the requirement here that derived classes call thread_.join() and do something different in the base class? Question 2 - What happens to the execution of the thread, when an exception is thrown from the thread that owns boost::thread object or the boost::thread object is destroyed? I'll probably have more questions as I progress.

1 0

Re: [Boost-users] [Containers Library Review] The review of the Containers library by Ion Gaztanaga starts today
by Ion Gaztañaga 03 Aug '11

03 Aug '11

El 03/08/2011 14:41, Mathias Gaunard escribió: > I think it might be good for the people not quite ready to hop onto the > C++0x bandwagon yet. > Plus sometimes it's good to be able to rely on a single portable > reference implementation that actually works with stateful allocators > etc., while it is implementation-defined whether the standard one does. Now that the new standard is nearly finished, the idea is to make them fully compliant, backport to C++03 all possible features and also have a library to experiment new proposals (N1953: Upgrading the Interface of Allocators using API Versioning and N2045: Improving STL allocators), enhancement functions, etc. Best, Ion

2 1

[multi-index][foreach] Iterating over a sequence index (worked in 1.46, broke in 1.47)
by Maxime van Noppen 03 Aug '11

03 Aug '11

Hi, I use BOOST_FOREACH to iterate of a BMI with a sequence index. The code used to work with Boost 1.46 and before, but broke with Boost 1.47. Am I doing something wrong ? ------------------------ #include <iostream> # include <boost/multi_index/hashed_index.hpp> # include <boost/multi_index/member.hpp> # include <boost/multi_index/sequenced_index.hpp> # include <boost/multi_index_container.hpp> # include <boost/foreach.hpp> using namespace ::boost::multi_index; typedef multi_index_container< int, indexed_by< sequenced<> > > bmi_t; typedef bmi_t::nth_index<0>::type seq_idx; const seq_idx& ret(const seq_idx& idx) { return idx; } int main() { bmi_t b; seq_idx& seq = b.get<0>(); // Works BOOST_FOREACH (int i, seq) std::cout << i << std::endl; // Doesn't compile BOOST_FOREACH (int i, ret(seq)) std::cout << i << std::endl; } ------------------------ Note that the offending part is the 'ret(seq)', without it, the code compiles. The error with g++ 4.6.1 is: > In file included from bmi.cc:9:0: > /home/yabo/dev/boost/usr/include/boost/multi_index/sequenced_index.hpp: In destructor ‘boost::foreach_detail_::simple_variant<T>::~simple_variant() [with T = boost::multi_index::detail::sequenced_index<boost::multi_index::detail::nth_layer<1, int, boost::multi_index::indexed_by<boost::multi_index::sequenced<> >, std::allocator<int> >, boost::mpl::vector0<mpl_::na> >]’: > /home/yabo/dev/boost/usr/include/boost/foreach.hpp:256:8: instantiated from here > /home/yabo/dev/boost/usr/include/boost/multi_index/sequenced_index.hpp:561:3: error: ‘boost::multi_index::detail::sequenced_index<SuperMeta, TagList>::~sequenced_index() [with SuperMeta = boost::multi_index::detail::nth_layer<1, int, boost::multi_index::indexed_by<boost::multi_index::sequenced<> >, std::allocator<int> >, TagList = boost::mpl::vector0<mpl_::na>]’ is protected > /home/yabo/dev/boost/usr/include/boost/foreach.hpp:586:13: error: within this context > /home/yabo/dev/boost/usr/include/boost/multi_index/sequenced_index.hpp: In constructor ‘boost::foreach_detail_::simple_variant<T>::simple_variant(const T&) [with T = boost::multi_index::detail::sequenced_index<boost::multi_index::detail::nth_layer<1, int, boost::multi_index::indexed_by<boost::multi_index::sequenced<> >, std::allocator<int> >, boost::mpl::vector0<mpl_::na> >]’: > /home/yabo/dev/boost/usr/include/boost/foreach.hpp:648:95: instantiated from ‘boost::foreach_detail_::auto_any<boost::foreach_detail_::simple_variant<T> > boost::foreach_detail_::contain(const T&, bool*) [with T = boost::multi_index::detail::sequenced_index<boost::multi_index::detail::nth_layer<1, int, boost::multi_index::indexed_by<boost::multi_index::sequenced<> >, std::allocator<int> >, boost::mpl::vector0<mpl_::na> >]’ > bmi.cc:28:3: instantiated from here > /home/yabo/dev/boost/usr/include/boost/multi_index/sequenced_index.hpp:549:3: error: ‘boost::multi_index::detail::sequenced_index<SuperMeta, TagList>::sequenced_index(const boost::multi_index::detail::sequenced_index<SuperMeta, TagList>&) [with SuperMeta = boost::multi_index::detail::nth_layer<1, int, boost::multi_index::indexed_by<boost::multi_index::sequenced<> >, std::allocator<int> >, TagList = boost::mpl::vector0<mpl_::na>]’ is protected > /home/yabo/dev/boost/usr/include/boost/foreach.hpp:571:9: error: within this context > /home/yabo/dev/boost/usr/include/boost/multi_index/sequenced_index.hpp: In copy constructor ‘boost::foreach_detail_::simple_variant<T>::simple_variant(const boost::foreach_detail_::simple_variant<T>&) [with T = boost::multi_index::detail::sequenced_index<boost::multi_index::detail::nth_layer<1, int, boost::multi_index::indexed_by<boost::multi_index::sequenced<> >, std::allocator<int> >, boost::mpl::vector0<mpl_::na> >, boost::foreach_detail_::simple_variant<T> = boost::foreach_detail_::simple_variant<boost::multi_index::detail::sequenced_index<boost::multi_index::detail::nth_layer<1, int, boost::multi_index::indexed_by<boost::multi_index::sequenced<> >, std::allocator<int> >, boost::mpl::vector0<mpl_::na> > >]’: > /home/yabo/dev/boost/usr/include/boost/foreach.hpp:256:8: instantiated from ‘boost::foreach_detail_::auto_any<boost::foreach_detail_::simple_variant<T> > boost::foreach_detail_::contain(const T&, bool*) [with T = boost::multi_index::detail::sequenced_index<boost::multi_index::detail::nth_layer<1, int, boost::multi_index::indexed_by<boost::multi_index::sequenced<> >, std::allocator<int> >, boost::mpl::vector0<mpl_::na> >]’ > bmi.cc:28:3: instantiated from here > /home/yabo/dev/boost/usr/include/boost/multi_index/sequenced_index.hpp:549:3: error: ‘boost::multi_index::detail::sequenced_index<SuperMeta, TagList>::sequenced_index(const boost::multi_index::detail::sequenced_index<SuperMeta, TagList>&) [with SuperMeta = boost::multi_index::detail::nth_layer<1, int, boost::multi_index::indexed_by<boost::multi_index::sequenced<> >, std::allocator<int> >, TagList = boost::mpl::vector0<mpl_::na>]’ is protected > /home/yabo/dev/boost/usr/include/boost/foreach.hpp:578:13: error: within this context Note that with clang++ 2.9 the code doesn't compile at all either with Boost 1.46 or Boost 1.47. Thanks! -- Maxime

6 12

[Concept] Ignoring return types
by Robert Jones 03 Aug '11

03 Aug '11

I have a template that I instantiate with a type that has to be nullary callable, so template <typename NullaryCallable> struct X { /*....*/ }; I'd like to be a good boy scout here, so I should constrain the template parameter, so template <typename NullaryCallablle> struct X { BOOST_CONCEPT_ASSERT(( Generator<NullaryCallable, void> )); // ... }; However, that constrains it to be nullary callable and returning void, and I'd prefer to avoid the void condition. Is all that sensible, true, and fixable? Thx - Rob.

1 0

#define BOOST_ASSERT_MSG_OSTREAM std::cout - message is not displayed
by asif saeed 03 Aug '11

03 Aug '11

Hi, After I have #defined BOOST_ASSERT_MSG_OSTREAM std::cout, using BOOST_ASSERT_MSG with a customized message does not display the message and, instead, I get the following message from Visual C++ 2010 Express: R6010 Abort() has been called What can I do to display the customized message? Best, Asif

1 0

Boost Book - comments?
by Robert Jones 03 Aug '11

03 Aug '11

Morning All Does anyone have any knowledge of this book? http://www.amazon.co.uk/Boost-C-Libraries/dp/3639942310/ref=sr_1_7?s=books&… <http://www.amazon.co.uk/Boost-C-Libraries/dp/3639942310/ref=sr_1_7?s=books&…>It's genesis, currency, provenance, and possibly a few review-like comments? Thx - Rob.

2 2

Re: [Boost-users] boost.regex with ICU memory cleanup on windows
by Alex Perry 03 Aug '11

03 Aug '11

John Maddock wrote on Tue, 2 Aug 2011 12:14:53 +0100 > There are a number of issues here: > > 1) Your call to u_cleanup() occurs while a u32regex object is still in existence, > so any ICU data being cached is actually still being used at that point. I couldn't get u_cleanup() to work anywhere - ie BOOST_AUTO_TEST_CASE( u32_regex ) { { boost::u32regex re( boost::make_u32regex("\\d{3}")); } u_cleanup(); } Or having u_cleanup() in a fixture teardown (which is how it was in the original code) doesn't seem to make any difference > 2) Boost.Regex does cache some internal data for improved performance - > this is relatively small and gets cleared after main() exits. > 3) Point (2) means that a call to _CrtDumpMemoryLeaks() before main exits > will report leaks, where as using something like: > > struct cleanup > { > ~cleanup() > { > _CrtDumpMemoryLeaks(); > } > }; > > cleanup c; The boost unit test framework does appear to do the memory dump in a destructor of a static object - I guess whether the regex library statics are destructed first depends on the order of loading - not sure if there is any easy way of ensuring that the unit test framework is destructed last (perhaps if I link to UTF as a static library?). > 4) Other leak detectors such as valgrind and VLD report no errors (and give > much more useful reports than the brain-dead MS ones IMO). > > HTH, John. :-) yes I agree - my current solution is --detect_memory_leaks=0 when running the unit tests - which at least stops the report. I was hoping that this was a reasonably common issue and there was some clean up function (like u_cleanup()) specifically for the regex library but if not can live with switching off memory loss detection. Thanks a lot for the help here though - it is much appreciated. Alex

2 1

Re: [Boost-users] [Repost][Boost][Serialization] ASSERTtriggered during reading 1.40 binary archive w/ Boost 1.47
by marc.viala＠sfr.fr 03 Aug '11

03 Aug '11

> De la part de Pfligersdorffer, Christian > > We were facing similar problems jumping from 1.36 to 1.45. > Binary archive backwards compatibility is broken in a few places. > > But: it is fixable. We may provide a patch Thanks Christian for your reply to this annoying issue. If you confirm that the backward compatibility is broken for Boost.Serialization #1.40 to #1.47 then *Yes* I would really appreciate any king of patch to address this issue. Looking the Boost.Serialization code, my first feeling would be to patch the implementation of basic_binary_iarchive::load_override(class_id_type & t, int version) for the library_version_type(5) ('5' stands for the library version for the release #1.40) but maybe this patch is too naïve and insufficient. If you can send me back a patch for this issue, I'll use it ASAP. > is there a TRAK ticket? I'm not sure but the ticket #5567 (https://svn.boost.org/trac/boost/ticket/5567) seems to address this bug. Thanks in advance and best regards, Marc Viala

1 0

Re: [Boost-users] [Repost][Boost][Serialization] ASSERT triggeredduring reading 1.40 binary archive w/ Boost 1.47
by Pfligersdorffer, Christian 03 Aug '11

03 Aug '11

We were facing similar problems jumping from 1.36 to 1.45. Binary archive backwards compatibility is broken in a few places. But: it is fixable. We may provide a patch - is there a TRAK ticket? Regards, -- Christian Pfligersdorffer Software Engineering www.eos.info > -----Ursprüngliche Nachricht----- > Von: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] Im Auftrag von > Marc Perso > Gesendet: Mittwoch, 3. August 2011 07:30 > An: boost-users(a)lists.boost.org > Betreff: [Boost-users] [Repost][Boost][Serialization] ASSERT triggeredduring reading 1.40 binary archive > w/ Boost 1.47 > > Let me forward this message posted few days ago since nobody has confirmed > that the issue described hereafter exists. I would really appreciate if > someone could take a look (maybe Mr Robert Ramey) and give some advice on > this subject. > > Best regards, > > Marc Viala > > ------------------------------------------------------------------------ > > Hello Booster, > > We are trying to jump from Boost 1.40 to Boost 1.47 but we are facing an > issue: an ASSERT is raised in debug mode when reading back binary archive > generated by Boost.Serialization 1.40 with the Boost.Serialization 1.47. > This ASSERT is at line 116 in basic_archive.hpp: > > BOOST_ASSERT(t_ <= boost::integer_traits<base_type>::const_max) > > And it occurs with the following platform: MSVC 8.0 and Windows XP/32bits or > Win7/64bits. > > Looking at the load_override and save_override implementations for > class_id_type in #1.40, they seem loading and saving an 'int_least16_t' > (equiv. to a short for our platform) while load_override(class_id_type) for > #1.47 attempts to read an 'int' (file: basic_binary_iarchive.hpp @ line 98). > > My questions are: > - This assert suggests that we can't read back previous binary archives > (#1.40 at least) with Boost.Serialization 1.47, is this a known pending > issue for Boost.Serialization? > > - If yes, how we can manage that and how we can complete the migration to > 1.47 in our case (it should be noted that we must be able to read back our > 1.40 binary archives)? Is there any known patch for this problem? > > Any assistance will be greatly appreciated. > > Best regards, > > Marc Viala > > PS: I'm not sure but ticket #5567 seems already opened on this issue but has > not been yet fixed (https://svn.boost.org/trac/boost/ticket/5567) > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Boost.Tokenizer / Sep - Compile-time errors ...
by asif saeed 03 Aug '11

03 Aug '11

Hi, Here is a piece of code that _only_ works when I provide it a hard-coded constant ";": typedef boost::char_separator<char_type_t> sep_type_t; typedef boost::tokenizer<sep_type_t> tokenizer_t; sep_(pa_->separator_.c_str()), t_(messageString,sep_), i_(t_.begin()) It wouldn't work with the separator passed in a variable (pa_->separator.c_str()). Tokenizer wouldn't work even if I initialize a const char* with a ";" and then pass that const char *variable to sep_ above. It gives me the following errors on if I pass separator in a variable: error C2780: 'bool boost::char_separator<Char>::operator ()(InputIterator &,InputIterator,Token &)' : expects 3 arguments - 1 provided Any idea how I can pass it a separator in a variable? Best, Asif

2 2

[Repost][Boost][Serialization] ASSERT triggered during reading 1.40 binary archive w/ Boost 1.47
by Marc Perso 03 Aug '11

03 Aug '11

Let me forward this message posted few days ago since nobody has confirmed that the issue described hereafter exists. I would really appreciate if someone could take a look (maybe Mr Robert Ramey) and give some advice on this subject. Best regards, Marc Viala ------------------------------------------------------------------------ Hello Booster, We are trying to jump from Boost 1.40 to Boost 1.47 but we are facing an issue: an ASSERT is raised in debug mode when reading back binary archive generated by Boost.Serialization 1.40 with the Boost.Serialization 1.47. This ASSERT is at line 116 in basic_archive.hpp: BOOST_ASSERT(t_ <= boost::integer_traits<base_type>::const_max) And it occurs with the following platform: MSVC 8.0 and Windows XP/32bits or Win7/64bits. Looking at the load_override and save_override implementations for class_id_type in #1.40, they seem loading and saving an 'int_least16_t' (equiv. to a short for our platform) while load_override(class_id_type) for #1.47 attempts to read an 'int' (file: basic_binary_iarchive.hpp @ line 98). My questions are: - This assert suggests that we can't read back previous binary archives (#1.40 at least) with Boost.Serialization 1.47, is this a known pending issue for Boost.Serialization? - If yes, how we can manage that and how we can complete the migration to 1.47 in our case (it should be noted that we must be able to read back our 1.40 binary archives)? Is there any known patch for this problem? Any assistance will be greatly appreciated. Best regards, Marc Viala PS: I'm not sure but ticket #5567 seems already opened on this issue but has not been yet fixed (https://svn.boost.org/trac/boost/ticket/5567)

1 0

Time management using posix time
by Sarkar, Arup 03 Aug '11

03 Aug '11

Hi: This is what is I am trying to achieve. I would like to run the program for 6 minutes, within the six minutes I would like to toggle for 2 minutes data operation and for 1 minute trade operation, so there will be 2 cycle of data operation and 2 cycle of trade operation. I am setting and getting the ptime outside the main program, but what is happening is that the getPtime of the template class is always return the +2 minutes of the current time, that is why diff is never reducing less than 2 minutes, why is that happening, the setter have been instantiated only once. I would really appreciate if someone can help me out. [code] // boost_example.cpp : Defines the entry point for the console application. // #include "boost/date_time/posix_time/posix_time.hpp" #include <iostream> #include <stdio.h> #include <stdio.h> #include "windows.h" using namespace std; template <typename ptime_type> class timeManagement { private: ptime_type tradingTime; public: timeManagement(){}; void setPtime (const ptime_type& _val){tradingTime = _val; } ptime_type const& getPtime() {return (tradingTime);} ~timeManagement(){}; }; int main() { bool btradingIndicator = false; std::ostringstream msg; using namespace boost::posix_time; const ptime start = second_clock::local_time(); time_duration td = minutes(6); time_duration tdDataCollection = minutes(2); time_duration tdTrading = minutes(1); bool bTradingIndicator = false; const ptime end = start + td; const ptime tTimeWindow = start + tdDataCollection; int i = 0; int switchTime = 0; timeManagement <ptime> tradingWindow; tradingWindow.setPtime(tTimeWindow); //std::cout << tradingWindow.getPtime() << std::endl; while(second_clock::local_time() <= end){ ptime currentTime = second_clock::local_time(); time_duration diff = tradingWindow.getPtime() - currentTime; if(diff.total_seconds() >= 0 && !bTradingIndicator){ std::cout << "Data.) " << currentTime << "|" << tradingWindow.getPtime() << "|" << diff << std::endl; }else{ const ptime tTimeWindow1 = currentTime + tdTrading; tradingWindow.setPtime(tTimeWindow1); bTradingIndicator = true; } if(diff.total_seconds() >= 0 && bTradingIndicator){ std::cout << "Trade.) " << diff << std::endl; }else{ const ptime tTimeWindow2 = currentTime + tdDataCollection; tradingWindow.setPtime(tTimeWindow2); bTradingIndicator = false; } } std::cout << "Start Time: " << start << std::endl; std::cout << "End Time: " << end << std::endl; std::cout << "Time Now: "<< end << std::endl; return 0; } [/code] Regards, Arup *"I don't need to know everything, I just need to KNOW where to find it, when I need it"*. -*Albert Einstein *

1 0

Re: [Boost-users] What's wrong with this simple multithreaded function that uses regex?
by Andrew Yancy 03 Aug '11

03 Aug '11

>I don't see anything obviously wrong with that. My only question, is you >say BOOST_HAS_THREADS is defined, are you defining it, or is Boost.Config >defining it (if Boost.Config *isn't* setting it, then your project >settings >are wrong for multithreaded code)? Are you selecting the regex lib to >link >to manually or letting the auto-linking code do it's work (for minimum >chances of bad things happening you should let the auto-linking code >select >the correct binary)? >HTH, John. >You should use _beginthread or _beginthreadex to start C++ thread when >using >MSVC. >CreateThread is too low level and does not do the per thread >initialization >required. If you read MSDN documentation it explain why CreateThread >cannot >be use with C++ program. >Daniel Anderson Thanks for the replies John and Daniel. I've reinstalled boost 1.47 making sure that all the multithreaded options were built and am using _beginthreadex() now, but the exact same problem seems to occur where the code snippet below crashes if and only if boost::regex_match() is called. I am not defining BOOST_HAS_THREADS in my code, it is defined automatically although I'm not sure how exactly. Also, as far as I know I am not manually linking to the necessary libraries; all I do is tell MSVC to look in "C:\Program Files\boost\boost_1_47_0\stage\lib" for additional libraries so presumably it chooses whichever one it needs. There are no thread or boost-related warnings in the build. Any other ideas? I really appreciate the help~ ... static const boost::regex expression("^[0-9]+"); ifstream myfile(x); //x is a different file name for every thread string line; if(myfile.is_open()) { while(myfile.good()) { getline(myfile, line); if(boost::regex_match(line, expression)) { //do stuff } } myfile.close(); } ...

2 2

[program_options] Best practices, esp. for multi-app-projects?
by Carlos Franke 02 Aug '11

02 Aug '11

I am wondering if there is a recommended way how the boost::program_options library should be integrated in a (relatively) complex project. To be more specific, these are my situation and my requirements: – A C++ project consisting of several applications, which are to share many, but not all options. – The interface to the options used in each app's code should be as boost-unspecific (i. e. abstract) as possible, so that I could later switch to another option library without having to edit much more than one file. – The option data should be somehow encapsulated. After pondering on this task for quite some time, I came up with this: – A single header file "options.h" shared by all the applications, providing a function read_options(int argc, char* argv[], const po::options_description& local_options = 0) , which scans the command line and the usual configuration files* for the common options (which are defined in the same header file, of course) as well asoptional app-specific options, and saves them (next paragraph). *(There is of course the problem of each app's name being part of its config-file's name. I found a solution for this, but I am not sure if it is relevant here. Or is it?) – Regarding the encapsulation, I found any kind of class or struct containing the options (possibly with get and set methods) unsuitable or overkill, as I would have to deal with instantiation and possible problems of multiple instantiation (singleton?). Also, I did not feel the need for the security provided by get and set methods. So what I did is: put all option variables in one namespace, like this: namespace options { int option1; std::string option2; ///... } A namespace has the further great advantage of being extendable after creation. Programme-specific options can be added easily. So in the end, in each programme I only have to do: //optional: define local options namespace options { /* . . . */ } po::options_description my_options /* . . . */ ; //read and save options: options::read_options(argc, argv, my_options) //from now on access the options' values by //options::option1; As I see it, this approach has only two drawbacks: – In each programme's code I have to deal with options twice: 1) declare the storage variables in the options namespace (globally); 2) declare local options_description and call read_options (in the main function). – There is no way to tell if the option variables are in a valid state, unless one is sure that read_options has been called and has set all values (at least to valid default values). I am inclined to tolerate the first issue and resolve the second by: – not using "default_value" in any po::options_description – instead intializing the option variables with their default values. That way, at any time each option variable either stores its default value or the assigned to it from the command line or a configuration file. Oh my, that ended up much longer than I expected. Those of you who read this far: What are your thoughts about using boost::program_options in general and about my particular approach? Regards! Carlos Franke

1 0

[units] derived_dimension<volume_dimension, 1> units showing as "dimensionless"
by Michael Powell 02 Aug '11

02 Aug '11

Units users, I'm sure this is an include I am missing somewhere. I've got a derived physical dimension defined as derived_dimension<volume_dimension,1>, and the corresponding unit<my_dimension,si::system>, however the to_string() of the quantity shows "dimensionless". I am expecting this should be "m^3"? Regards, Michael

1 0

[units] setting up a derived dimensionless with a custom name/symbol
by Michael Powell 02 Aug '11

02 Aug '11

Boost::Units users, How would we go about setting up a custom unit with its own name/symbol? We would derive another unit that incorporates this one and probably one of the built-in ones. So we might have something like "volume per custom units", or "custom units per time". * From the sounds of things, we would need to setup a custom base unit with its own info struct defining name() and symbol()? * Probably starting out included in the SI system to get the thing working; plausibly extending into other systems/views as we get further along. I'm making an effort to keep our local usages/extensions to the boost::units framework in the same style/structure, so as to keep things flowing well into our application. I am also using meter as a template, but I'm not sure that's quite the template which would get us what we need? Yes, no, maybe? Any insights? Thank you... Regards, Michael

1 0

Building boost::posix_time with nano second support
by Matthias Dörfelt 02 Aug '11

02 Aug '11

Hello, I want to use nanoseconds from boost::posix_time but as stated in the reference, you have to define BOOST_DATE_TIME_POSIX_TIME_STD_CONFIG to make that work. Unfortunatelly I don't have any idea where i have to define that variable in the build process. I build boost 1.47.0 like this on osx snow leopard: ./b2 macosx-version=10.6 link=static address-model=32_64 threading=multi stage So, where do I have to define the discussed variable to enable nanosecond support? Offtopic: I also noticed that adress-model=32_64 does not seem to work since all the produced static libs are x86_64 only.- Any ideas about how to fix that? Thank you!

1 0

Delayed/Lazy Function Call
by John M. Dlugosz 02 Aug '11

02 Aug '11

Consider something like this: typedef std::tr1::function<void ()> CapsuleFunc; class worker_thread_queue; class forwarder { worker_thread_queue* queue; const NotifyFunc f; public: forwarder (worker_thread_queue* queue, const NotifyFunc f) : queue(queue), f(f) {} void operator() (uint32_t extended_ID, State_t newstate, State_t oldstate); }; class worker_thread_queue { // doesn't really work, just for illustration public: worker_thread_queue() { // really, would create a thread and thread-safe FIFO } // Calling submit will put f in a queue, and that queue is processed by the // worker thread. It removes each item in FIFO order and executes them. void submit (const CapsuleFunc& f) { /* but it's just an example */ } // Calling wrap will return another function that when executed will call submit(f) on this instance. NotifyFunc wrap (const NotifyFunc& f) { forwarder x (this, f); return x; } }; void forwarder::operator() (uint32_t extended_ID, State_t newstate, State_t oldstate) { CapsuleFunc x= std::tr1::bind (f, extended_ID, newstate, oldstate); queue->submit (x); } // later... worker_thread_queue work_queue; work_queue.wrap(&foo); Presuming a compiler that doesn't have Lambda functions supported, is there some nicer way to acheive the effect shown by 'wrap'? Given a function object f and a object q, I want to create a new function object that when invoked will bind its arguments and call q->submit with the bound-up form. I've seen forwarders throughout Boost; is there a publicly available one that I can use? Or some kind of "delayed apply" that can be called like bind, with the thing to be built up? I recall there is a full heavy duty library for lazy evaluation but don't recall its name. But I'm also wondering if there is a specific (lighter weight or already being used within the Boost libraries I'm already using) mechanism for this. —John

1 0

access violation with asio
by Gianni Ambrosio 02 Aug '11

02 Aug '11

Hi All, can anybody explain me please why I get an access violation in the following code? And why if I enable the std::cout in the stream_handler destructor the code work fine without exception? I'm developing on windows XP, VS 2005. Regards Gianni Here is the code: #include <boost/asio.hpp> #include <boost/bind.hpp> #include <boost/thread.hpp> #include <boost/date_time/posix_time/posix_time_types.hpp> #include <iostream> typedef boost::shared_ptr<boost::asio::ip::tcp::socket> tcp_socket_ptr; class stream_handler { public: stream_handler() : acceptor(io_service) { boost::asio::ip::tcp::endpoint endpoint = boost::asio::ip::tcp::endpoint(boost::asio::ip::tcp::v4(), 22222); acceptor.open(endpoint.protocol()); acceptor.set_option(boost::asio::ip::tcp::acceptor::reuse_address(true)); acceptor.bind(endpoint); acceptor.listen(); socket = tcp_socket_ptr(new boost::asio::ip::tcp::socket(io_service)); acceptor.async_accept(*socket, boost::bind(&stream_handler::handleAcceptForDebug, this, boost::asio::placeholders::error)); work = boost::shared_ptr<boost::asio::io_service::work>(new boost::asio::io_service::work(io_service)); thread = boost::thread(boost::bind(&boost::asio::io_service::run, &io_service)); } virtual ~stream_handler() { //std::cout << __FUNCTION__ << std::endl; io_service.stop(); } private: boost::asio::io_service io_service; boost::shared_ptr<boost::asio::io_service::work> work; boost::asio::ip::tcp::acceptor acceptor; boost::thread thread; tcp_socket_ptr socket; void handleAcceptForDebug(const boost::system::error_code& iError) {}; }; int main(int argc, char** argv) { stream_handler tcpsocket; return 0; }

2 3

Bizarre problem with range/adaptor/transformed.hpp
by John M. Dlugosz 02 Aug '11

02 Aug '11

I've traced a problem in my program to the inclusion of #include "boost/range/adaptor/transformed.hpp" Nothing is using the features in it (such things are removed from the test case build I'm using to get to the bottom of it). It compiles just as well with or without the line. But if the file is included, the program is broken. If I omit it, then the program works fine. Any suggestions would be welcome.

3 6

boost.regex with ICU memory cleanup on windows
by Alex Perry 02 Aug '11

02 Aug '11

Hi, I recently asked this on stack overflow boost with icu u32_regex memory leak / cache on Win32<http://stackoverflow.com/questions/6867664/boost-with-icu-u32-regex-memory-…> but haven't been able to solve issue yet so thought I would ask here as well. The problem I'm having is that I can't seem to clean up the ICU data when it is loaded by boost regex using the optional icu linkage to support Unicode regex's. I'll copy the example source I posted above:- #define BOOST_TEST_MAIN //Ask boost unit test framework to create a main for us #define BOOST_ALL_DYN_LINK //Ask boost to link to dynamic library rather than purely header support where appropriate #include <boost/test/auto_unit_test.hpp> #include <boost/regex.hpp> #include <boost/regex/icu.hpp> //We use icu extensions to regex to support unicode searches on utf-8 #include <unicode/uclean.h> //We want to be able to clean up ICU cached objects BOOST_AUTO_TEST_CASE( standard_regex ) { boost::regex re( "\\d{3}"); } BOOST_AUTO_TEST_CASE( u32_regex ) { boost::u32regex re( boost::make_u32regex("\\d{3}")); u_cleanup(); //Ask the ICU library to clean up any cached memory } Which may be compiled at command prompt (cl version 16 from vs2010) with appropriate directories inserted if not pathed in on machine. cl test.cpp /I[BOOST HEADERS PATH] /I[ICU HEADERS] /EHsc /MDd -link /LIBPATH:[BOOST LIB PATH] [ICU LIB PATH]icuuc.lib The problem I have with this is that the u_cleanup() does not cleanup so the unit test framework reports memory leaks (at least that is what I think is going on) :- Just compiling the 1st test case will work perfectly - adding in the 2nd test case (with or without the u_cleanup() ) will generate a memory leak report Running 2 test cases... *** No errors detected Detected memory leaks! Dumping objects -> {778} normal block at 0x00668530, 28 bytes long. Data: < 0N W > 00 00 00 00 30 4E C2 57 00 00 00 00 01 00 00 00 {777} normal block at 0x004C5AF8, 14 bytes long. Data: <icudt46l-coll > 69 63 75 64 74 34 36 6C 2D 63 6F 6C 6C 00 {776} normal block at 0x004C5200, 5 bytes long. Data: <root > 72 6F 6F 74 00 {775} normal block at 0x004C9B30, 60 bytes long. Data: < RL ZL > 00 52 4C 00 F8 5A 4C 00 00 00 00 00 00 00 00 00 ... rest removed for clarity As it says in comment on original post icu appears to be loaded as a dynamic link so I can't see why u_cleanup() would not work - alternatively I can't find any calls in boost::regex library which would allow me to ask it to clean up icu cache. Thanks in advance for any help. Alex

2 1

program_options, parse up to first non-option
by Tow Mater 02 Aug '11

02 Aug '11

Can program_options be used to parse command line elements up to the first non-option that is not an option argument?

2 2

Boost::Tokenizer / "string iterators incompatible" error on Visual C++ 2010 Express - runs ok on gcc4.6.0
by asif saeed 02 Aug '11

02 Aug '11

Hi, The following piece of code is giving me "string iterators incompatible" error: ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// #include <iostream> #include <string> #include <boost/tokenizer.hpp> class Base { public: typedef boost::char_separator<char> sep_type_t; typedef boost::tokenizer<sep_type_t> tokenizer_t; Base(std::string s) : sep_(";"), tok_(s,sep_), i_(tok_.begin()) { } std::string nextToken() { if (i_!=tok_.end()) return *i_++; else return ""; } protected: sep_type_t sep_; tokenizer_t tok_; tokenizer_t::iterator i_; }; class Sub : public Base { public: Sub(std::string s) : Base(s) { std::string t = nextToken(); std::string u = nextToken(); std::string v = nextToken(); } void doSomething() { int x = 0; x +=1; } }; int main (int argc, char **argv) { Sub x("ASIF;Sohail;Kaleem;Maryam;Irfan;Khurram"); x.doSomething(); return 0; } ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// This code is compiling and running fine on GCC 4.6.0 / Fedora 15 / 64-bit. I hope somebody here will help me out on this. Best regards, Asif

3 4

Help with bind usage
by John M. Dlugosz 02 Aug '11

02 Aug '11

Suppose I have something that expects a general function object that takes three parameters. I have a function that takes one parameter, and I don't care about the other two. How do I get an instance func that when called as func(a,b,c) will end up calling my function foo as foo(a) and throw away the other two? If I use bind, I wind up with a functor that takes fewer arguments than the original. But here I have more.

2 1

Article on Boost.Asio in German computer magazine c't
by Boris Schaeling 01 Aug '11

01 Aug '11

I submitted today an article on Boost.Asio which will be published in the German computer magazine c't. I don't know yet in which edition but will tell on http://www.highscore.de/feed.atom. There may be more articles on Boost in c't in the future which I'll announce on my RSS feed then only (not to spam these lists). All of this hopefully helps to increase media coverage of Boost in the longterm. This again could help if for example BoostCon grows into something bigger. For now the article on Boost.Asio is a small step-stone. :) Boris

1 0

[range] range metafunctions and reference types
by Nathan Ridge 01 Aug '11

01 Aug '11

Hello, The range metafunctions currently do not work on range reference types. For example, the following: #include <vector> #include <boost/range/metafunctions.hpp> typedef boost::range_iterator<std::vector<int>&>::type iter_t; Fails with the errors: In file included from lib/boost/boost/range/iterator.hpp:23:0, from lib/boost/boost/range/metafunctions.hpp:18, from test4.cpp:2: lib/boost/boost/mpl/eval_if.hpp: In instantiation of 'boost::mpl::eval_if_c<false, boost::range_const_iterator<std::vector<int>&>, boost::range_mutable_iterator<std::vector<int>&> >': lib/boost/boost/range/iterator.hpp:72:63: instantiated from 'boost::range_iterator<std::vector<int>&>' test4.cpp:4:49: instantiated from here lib/boost/boost/mpl/eval_if.hpp:60:31: error: no type named 'type' in 'boost::mpl::eval_if_c<false, boost::range_const_iterator<std::vector<int>&>, boost::range_mutable_iterator<std::vector<int>&> >::f_ {aka struct boost::range_mutable_iterator<std::vector<int>&>}' This behaviour is OK when you are doing things like this: template <typename Range> typename range_iterator<Range>::type some_function(const Range& r) { ... } because when called with a "const vector<T>&" argument, template argument deduction will deduce "Range" to be just "vector<T>", and this is what we call the metafunction on. Likewise, if some_function has a non-const version that takes a "Range&" argument, it works fine too. But in C++0x, rvalue references allow us to kill two birds with one stone and have just one function that accepts both const and non-const references: template <typename Range> typename range_iterator<Range>::type some_function(Range&& r) { ... } However, the template argument deduction rules for rvalue references are different: if the function is called with a "const vector<T>&" parameter, "Range" will be deduced as "const vector<T>&", i.e. the reference is preserved. But now range_iterator gives an error as indicated above, so we have to do something awkward and verbose like this: template <typename Range> typename range_iterator<typename remove_reference<Range>::type>::type some_function(Range&& r) { ... } Could the range metafunctions be modified to accept range reference parameters and remove the reference themselves? Thanks, Nate.

2 3

[Serialization] Linker error on BOOST_CLASS_EXPORT upgrading from 1.44.0
by Enrico Carrara 01 Aug '11

01 Aug '11

Hello, I am facing a problem with serialization as implemented in Boost 1.47.0 which I did not experience in version 1.44.0. The problem appears as a series of linker errors (Visual C++ 8.0 (VS2005), WinXP 32bit): 1>Compiling... 1>Model_SerializationXml.cpp 1>Model_SerializationTxt.cpp 1>Compiling manifest to resources... 1>Linking... 1>Model_SerializationXml.obj : error LNK2005: "public: static struct boost::archive::detail::extra_detail::guid_initializer<class sm::CompLoad_Test> const & const boost::archive::detail::extra_detail::init_guid<class sm::CompLoad_Test>::g" (?g@?$init_guid@VCompLoad_Test@sm@@@extra_detail@detail@archive@boost @@2ABU?$guid_initializer@VCompLoad_Test@sm@@@2345@B) already defined in Model_SerializationTxt.obj [...many more similar errors] The scenario is as follows: I have a considerable bunch of classes which must be serialized by means of both text and XML archives. To this purpose, I have two compilation units, "Model_SerializationTxt.cpp" and "Model_SerializationXml.cpp", as follows: ///////////////////////////////////////////////// // Model_SerializationTxt.cpp [...] #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/archive_exception.hpp> [...] #include "SerClassExport.h" [...] ///////////////////////////////////////////////// ///////////////////////////////////////////////// // Model_SerializationXml.cpp [...] #include <boost/archive/xml_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/archive_exception.hpp> [...] #include "SerClassExport.h" [...] ///////////////////////////////////////////////// ///////////////////////////////////////////////// // SerClassExport.h [...] // APPLICATION_DEPENDENT: Include here files // relevant to model classes to be exported // for serialization #include "Model_Root.h" #include "SM/SM_Node.h" [...Many more class definition headers] [...] #include <boost/serialization/export.hpp> // APPLICATION_DEPENDENT: Include here files // relevant to model classes to be exported // for serialization BOOST_CLASS_EXPORT(model::Root) BOOST_CLASS_EXPORT(sm::Node) [...Many more class export definitions] [...] ///////////////////////////////////////////////// The problem seems to be related to the fact that BOOST_CLASS_EXPORT is defined twice in my project. In Boost 1.44.0, struct guid_initializer was defined in "export.hpp" inside an anonymous namespace, while in Boost 1.47.0 - actually, since version 1.45.0 - the definition is inside namespace extra_detail, even if the comment above is unchanged: ///////////////////////////////////////////////// // export.hpp in Boost 1.44.0 [...] // Note INTENTIONAL usage of anonymous namespace in header. // This was made this way so that export.hpp could be included // in other headers. This is still under study. namespace { template<class T> struct guid_initializer [...] #define BOOST_CLASS_EXPORT_IMPLEMENT(T)\ namespace boost {\ namespace archive {\ namespace detail {\ namespace {\ template<>\ struct init_guid< T > {\ static guid_initializer< T > const & g;\ };\ guid_initializer< T > const & init_guid< T >::g =\ ::boost::serialization::singleton<\ guid_initializer< T >\ >::get_mutable_instance().export_guid();\ }}}}\ [...] ///////////////////////////////////////////////// ///////////////////////////////////////////////// // export.hpp in Boost 1.47.0 [...] // Note INTENTIONAL usage of anonymous namespace in header. // This was made this way so that export.hpp could be included // in other headers. This is still under study. namespace extra_detail { template<class T> struct guid_initializer [...] #define BOOST_CLASS_EXPORT_IMPLEMENT(T)\ namespace boost {\ namespace archive {\ namespace detail {\ namespace extra_detail {\ template<>\ struct init_guid< T > {\ static guid_initializer< T > const & g;\ };\ guid_initializer< T > const & init_guid< T >::g =\ ::boost::serialization::singleton<\ guid_initializer< T >\ >::get_mutable_instance().export_guid();\ }}}}\ [...] ///////////////////////////////////////////////// I guess that this might have a role in originating the linker problem. How can I avoid this error? I already tried including the list of BOOST_CLASS_EXPORT only once, i.e in Model_SerializationTxt.cpp only. This solved the linker problem, but serialization of data in XML was then impossible (runtime error). Unfortunately, merging the two compilation units in one is not possible, because the compiler (Visual C++ 8.0) goes out of memory while compiling the big unit (process memory grows beyond 2GB). Is there, in your opinion, a solution or a workaround to this situation? Let me apologize for the very long mail, I did not succeed in shortening it further. Looking forward to any possible advice, thank you in advance for your attention. Enrico

2 5

Boost::Tokenizer - "string iterators incompatible"
by asif saeed 01 Aug '11

01 Aug '11

Hi, The following piece of code is giving me "string iterators incompatible" error: ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// #include <iostream> #include <string> #include <boost/tokenizer.hpp> class Base { public: typedef boost::char_separator<char> sep_type_t; typedef boost::tokenizer<sep_type_t> tokenizer_t; Base(std::string s) : sep_(";"), tok_(s,sep_), i_(tok_.begin()) { } std::string nextToken() { if (i_!=tok_.end()) return *i_++; else return ""; } protected: sep_type_t sep_; tokenizer_t tok_; tokenizer_t::iterator i_; }; class Sub : public Base { public: Sub(std::string s) : Base(s) { std::string t = nextToken(); std::string u = nextToken(); std::string v = nextToken(); } void doSomething() { int x = 0; x +=1; } }; int main (int argc, char **argv) { Sub x("ASIF;Sohail;Kaleem;Maryam;Irfan;Khurram"); x.doSomething(); return 0; } ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// This code is compiling and running fine on GCC 4.6.0 / Fedora 15 / 64-bit. I hope somebody here will help me out on this. Best regards, Asif

1 0

[units] How to multiply a quantity with a dimensionless factor
by Marcel 01 Aug '11

01 Aug '11

Hi, I'm new to boost and units and hope this is not too trivial. If I try to multiply a quantity with a dimensionless factor like quantity<length> a; quantity<length> b = 2.0 * b; I get compiler errors due to missing operator*. So I worked around this by using quantity<length> b = quantity<dimensionless>(2.0) * b; But I'm wondering if there is a easier and better readable way to do this? Thank you in advance, Marcel

2 3

Execution problem moving libraries
by Alessandro Candini 01 Aug '11

01 Aug '11

Hi everyone. I get a very tricky error with boost.thread. I can compile and execute perfectly a C++ program with the following comand line: g++ -Wall -fPIC -pedantic -g -O3 -DDEBUG -march=native -std=c++0x -lboost_thread -o myExecutable myExecutable.cpp But I have to move this software into another machine, and I thought it was possible to take dynamic libraries with it, in order to properly link them to the executable. I have a structure like the following: package | bin |- myExecutable etc |- libboost_thread.a |- libboost_thread.so -> libbost_thread.so.1.42.0 `- libboost_thread.so.1.42.0 And performing a proper export of LD_LIBRARY_PATH, it seems I obtain a correct link: ldd myExecutable ... libboost_thread.so.1.42.0 => ../etc/libboost_thread.so.1.42.0 (0x002cd000) ... But when I try to execute my software, I obtain the following error: /home/user/myExecutable symbol lookup error: /home/user/myExecutable: undefined symbol: _ZTIN10__cxxabiv115__forced_unwindE Do you have an idea of why this occurs? Have I to compile boost libraries in an uncommon way to make this situation work? Thank you. -- Alessandro Candini MEEO S.r.l. Via Saragat 9 I-44122 Ferrara, Italy Tel: +39 0532 1861501 Fax: +39 0532 1861637 http://www.meeo.it ======================================== "ATTENZIONE:le informazioni contenute in questo messaggio sono da considerarsi confidenziali ed il loro utilizzo è riservato unicamente al destinatario sopra indicato. Chi dovesse ricevere questo messaggio per errore è tenuto ad informare il mittente ed a rimuoverlo definitivamente da ogni supporto elettronico o cartaceo." "WARNING:This message contains confidential and/or proprietary information which may be subject to privilege or immunity and which is intended for use of its addressee only. Should you receive this message in error, you are kindly requested to inform the sender and to definitively remove it from any paper or electronic format."

4 5

[interprocess] garbage chars when extending interprocess strings?
by Anthony Foiani 01 Aug '11

01 Aug '11

I'm having a peculiar problem with interprocess strings. 0. Create the shared string type. typedef boost::interprocess::managed_shared_memory ShmManagerType; typedef char ShmCharType; typedef boost::interprocess::allocator< ShmCharType, ShmManagerType::segment_manager > ShmCharAllocatorType; typedef boost::interprocess::basic_string< ShmCharType, std::char_traits< ShmCharType >, ShmCharAllocatorType > ShmStringType; 1. Initial write succeeds. ShmStringType val; val = "x"; cout << quoteString( x ) << endl; // prints "x" as expected 2. When I overwrite the value with a longer value, the longer value is stored and the length is updated -- but a null character (\0) is inserted at the *old* length. ShmStringType x3( "xxx" ); val = x3; cout << quoteString( val ) << endl; // prints "x\0x" !!! 3. When I write the longer value again, it is stored correctly and there is no \0 in the middle of the string. val = x3; cout << quoteString( val ) << endl; // prints "xxx" as expected 4. The same thing happens if we try a longer value again: ShmStringType x5( "xxxxx" ); val = x5; cout << quoteString( val ) << endl; // prints "xxx\0x" val = x5 cout << quoteString( val ) << endl; // prints "xxxxx" Does this ring bells for anyone? On my embedded platform, I'm using: powerpc e300c3 Linux 2.6.36 eglibc 2.13 boost 1_44_0 g++ 4.5.1 And on my development workstation: intel x86-64 Linux 2.6.35.13-92.fc14 glibc 2.13-1 boost 1.44.0-8.fc14 gcc 4.5.1-4.fc14 Testing this on my development workstation, I see similar issues (although it's not always \0; in this case, I'm getting \xC0 junk characters. Odd!) Test case at: http://foiani.com/cpp/boost/InterProcStringTest.cpp Sample output: http://foiani.com/cpp/boost/ipst-out-ppc32.txt http://foiani.com/cpp/boost/ipst-out-x86_64.txt The output isn't the same: some cases work on one platform but not the other, and the garbage character introduced isn't always \0. Any ideas would be welcome. Testing with a more current boost is a bit problematic; if someone believes that it's been fixed in the mean time, I'll do my best to try with a modern boost. In the mean time, I'll just write the values twice, I guess. :) Thanks for your time and attention! Best regards, Tony

3 8

[Iterator]Can dereference() in iterator_adaptor return a temporary value?
by Remi 01 Aug '11

01 Aug '11

Hi, I'd like a const iterator that acts as a proxy by giving access to elements of type A as if they were elements of unrelated type B. In that case I guess the dereference() member function should return a temporary value, right? Would that be a correct implementation of the idea? Here I just want to access an array of SourceVertexType as if it were an array of VertexType. template<class VertexType> class ConstVerticesIterator : public boost::iterator_adaptor< ConstVerticesIterator<VertexType>, const SourceVertexType*, const VertexType > { private: friend class boost::iterator_core_access; VertexType dereference() const { const SourceVertexType& source_vertex( *base() ); return VertexType( source_vertex.x, source_vertex.y ); } public: explicit ConstVerticesIterator( const SourceVertexType* vertices ) : boost::iterator_adaptor< ConstVerticesIterator<VertexType>, const SourceVertexType*, const VertexType >( vertices ) {} };

2 2

translate C-code into objects
by Peter Foelsche 01 Aug '11

01 Aug '11

Dear All, I would like to translate some C-Code into objects. I did this already for functions and expressions: Writing template functions and passing my expression object as an argument. Now I want to do this for C-Code, which uses if-statements and variables. To do this, I would implement some template function for an if-statement. And some function for an assignment to a variable. Probably using enumerations to indicate the variable. Is this the right approach? Peter

5 6