- Boost-users - lists.boost.org

[serialization] When do I need to overload operators
by Sean Farrow 19 Sep '10

19 Sep '10

Hi: In trhe demo.cpp file in the Serialization examples, the << and >> operators are made friends of the gps_position class and are overridden. In what circumstances do I need to override these operators and when can I get away with just writing a Serialize template function. Regards Sean.

2 1

Performance of boost::serialization
by Daniel Herb 18 Sep '10

18 Sep '10

Hi! I'm having performance issues with boost::serilaization. First a short description what my data looks like: I serialize a container of boost::shared_ptr<Base> where i put polymorph objects in (no very deep hierarchy ~2 layers). The objects are ~40 byte each. The container has 100 elements in my test case. In the test application i can only serialize that container ~40 times per second. That's to slow for me because the data is used for the network communication. What i've found is this thread: http://old.nabble.com/-Serialization--Speedding-up-client-server-communicat… But it seems that i have to recreate the archive in my case because the data can get send, changed and send again. The documentation says that this behaviour can be disabled through disabling tracking. But that doesn't work for me because I use pointers. Robert Ramey also mentioned that implementing a lightweight version of stringstream could improve the performance. I liked to look at that but it seems that i'm missing something completely. class mystreambuf : public std::streambuf { public: virtual std::streamsize xsputn(const char*_Ptr, std::streamsize _Count) { } }; So this stream buffer does nothing right? But somehow serialization throughput is even worse with that implementation (compared to stringstream). I've never implemented a stream buffer so help would be nice. What are the requirements of boost::serialization for the stream buffer? Also generally it would be nice if you could share your oppinion if you think if the performance of boost::serialization can be tuned to serialize data for network communication. Is it only possible without polymorphism/shared_ptr? Any help is welcome! Thanks -- View this message in context: http://old.nabble.com/Performance-of-boost%3A%3Aserialization-tp29739639p29… Sent from the Boost - Users mailing list archive at Nabble.com.

3 4

libboost*-mt.so (thread safety)
by Stanisław Findeisen 18 Sep '10

18 Sep '10

Hi! It looks that in some older Boost versions (up to 1.40 or so) several shared objects were coming in 2 versions: with or without -mt suffix. For instance: libboost_filesystem-gcc42-1_34_1.so.1.34.1 libboost_filesystem-gcc42-mt-1_34_1.so.1.34.1 libboost_program_options-gcc42-1_34_1.so.1.34.1 libboost_program_options-gcc42-mt-1_34_1.so.1.34.1 libboost_regex-gcc42-1_34_1.so.1.34.1 libboost_regex-gcc42-mt-1_34_1.so.1.34.1 (These are the names from my Debian GNU/Linux installation, perhaps they are a bit different than when building from source.) This seems to no longer be the case with Boost 1.44. I've just built it from source passing threading=multi parameter to bjam, and can't see any -mt shared objects. This is what I have: drwxr-xr-x 2 ... 4096 ... 11:55 . drwxr-xr-x 4 ... 4096 ... 11:43 .. -rw-r--r-- 1 ... 118790 ... 11:49 libboost_date_time.a lrwxrwxrwx 1 ... 28 ... 11:48 libboost_date_time.so -> libboost_date_time.so.1.44.0 -rwxr-xr-x 1 ... 92296 ... 11:48 libboost_date_time.so.1.44.0 -rw-r--r-- 1 ... 294068 ... 11:50 libboost_filesystem.a lrwxrwxrwx 1 ... 29 ... 11:48 libboost_filesystem.so -> libboost_filesystem.so.1.44.0 -rwxr-xr-x 1 ... 171758 ... 11:48 libboost_filesystem.so.1.44.0 -rw-r--r-- 1 ... 534858 ... 11:51 libboost_graph.a lrwxrwxrwx 1 ... 24 ... 11:49 libboost_graph.so -> libboost_graph.so.1.44.0 -rwxr-xr-x 1 ... 379135 ... 11:49 libboost_graph.so.1.44.0 -rw-r--r-- 1 ... 286678 ... 11:52 libboost_math_c99.a -rw-r--r-- 1 ... 282978 ... 11:52 libboost_math_c99f.a lrwxrwxrwx 1 ... 28 ... 11:44 libboost_math_c99f.so -> libboost_math_c99f.so.1.44.0 -rwxr-xr-x 1 ... 133041 ... 11:44 libboost_math_c99f.so.1.44.0 -rw-r--r-- 1 ... 288144 ... 11:52 libboost_math_c99l.a lrwxrwxrwx 1 ... 28 ... 11:45 libboost_math_c99l.so -> libboost_math_c99l.so.1.44.0 -rwxr-xr-x 1 ... 132259 ... 11:44 libboost_math_c99l.so.1.44.0 lrwxrwxrwx 1 ... 27 ... 11:44 libboost_math_c99.so -> libboost_math_c99.so.1.44.0 -rwxr-xr-x 1 ... 137877 ... 11:44 libboost_math_c99.so.1.44.0 -rw-r--r-- 1 ... 1714884 ... 11:51 libboost_math_tr1.a -rw-r--r-- 1 ... 1723476 ... 11:52 libboost_math_tr1f.a lrwxrwxrwx 1 ... 28 ... 11:44 libboost_math_tr1f.so -> libboost_math_tr1f.so.1.44.0 -rwxr-xr-x 1 ... 295638 ... 11:44 libboost_math_tr1f.so.1.44.0 -rw-r--r-- 1 ... 1716390 ... 11:52 libboost_math_tr1l.a lrwxrwxrwx 1 ... 28 ... 11:44 libboost_math_tr1l.so -> libboost_math_tr1l.so.1.44.0 -rwxr-xr-x 1 ... 287712 ... 11:44 libboost_math_tr1l.so.1.44.0 lrwxrwxrwx 1 ... 27 ... 11:43 libboost_math_tr1.so -> libboost_math_tr1.so.1.44.0 -rwxr-xr-x 1 ... 287831 ... 11:43 libboost_math_tr1.so.1.44.0 -rw-r--r-- 1 ... 90942 ... 11:54 libboost_prg_exec_monitor.a lrwxrwxrwx 1 ... 35 ... 11:46 libboost_prg_exec_monitor.so -> libboost_prg_exec_monitor.so.1.44.0 -rwxr-xr-x 1 ... 77833 ... 11:46 libboost_prg_exec_monitor.so.1.44.0 -rw-r--r-- 1 ... 742886 ... 11:53 libboost_program_options.a lrwxrwxrwx 1 ... 34 ... 11:45 libboost_program_options.so -> libboost_program_options.so.1.44.0 -rwxr-xr-x 1 ... 440715 ... 11:45 libboost_program_options.so.1.44.0 -rw-r--r-- 1 ... 8868 ... 11:53 libboost_random.a lrwxrwxrwx 1 ... 25 ... 11:46 libboost_random.so -> libboost_random.so.1.44.0 -rwxr-xr-x 1 ... 13058 ... 11:45 libboost_random.so.1.44.0 -rw-r--r-- 1 ... 2102620 ... 11:50 libboost_regex.a lrwxrwxrwx 1 ... 24 ... 11:49 libboost_regex.so -> libboost_regex.so.1.44.0 -rwxr-xr-x 1 ... 1256561 ... 11:49 libboost_regex.so.1.44.0 -rw-r--r-- 1 ... 984416 ... 11:54 libboost_serialization.a lrwxrwxrwx 1 ... 32 ... 11:46 libboost_serialization.so -> libboost_serialization.so.1.44.0 -rwxr-xr-x 1 ... 624366 ... 11:46 libboost_serialization.so.1.44.0 -rw-r--r-- 1 ... 139202 ... 11:54 libboost_signals.a lrwxrwxrwx 1 ... 26 ... 11:46 libboost_signals.so -> libboost_signals.so.1.44.0 -rwxr-xr-x 1 ... 99503 ... 11:46 libboost_signals.so.1.44.0 -rw-r--r-- 1 ... 15498 ... 11:49 libboost_system.a lrwxrwxrwx 1 ... 25 ... 11:48 libboost_system.so -> libboost_system.so.1.44.0 -rwxr-xr-x 1 ... 20109 ... 11:48 libboost_system.so.1.44.0 -rw-r--r-- 1 ... 1476598 ... 11:49 libboost_test_exec_monitor.a -rw-r--r-- 1 ... 149246 ... 11:54 libboost_thread.a lrwxrwxrwx 1 ... 25 ... 11:47 libboost_thread.so -> libboost_thread.so.1.44.0 -rwxr-xr-x 1 ... 118667 ... 11:47 libboost_thread.so.1.44.0 -rw-r--r-- 1 ... 1634106 ... 11:54 libboost_unit_test_framework.a lrwxrwxrwx 1 ... 38 ... 11:47 libboost_unit_test_framework.so -> libboost_unit_test_framework.so.1.44.0 -rwxr-xr-x 1 ... 941323 ... 11:47 libboost_unit_test_framework.so.1.44.0 -rw-r--r-- 1 ... 2909510 ... 11:55 libboost_wave.a lrwxrwxrwx 1 ... 23 ... 11:48 libboost_wave.so -> libboost_wave.so.1.44.0 -rwxr-xr-x 1 ... 1686755 ... 11:48 libboost_wave.so.1.44.0 -rw-r--r-- 1 ... 694192 ... 11:54 libboost_wserialization.a lrwxrwxrwx 1 ... 33 ... 11:46 libboost_wserialization.so -> libboost_wserialization.so.1.44.0 -rwxr-xr-x 1 ... 464203 ... 11:46 libboost_wserialization.so.1.44.0 Is it so, that all Boost libraries are now thread safe?? Or maybe I overlooked some build options??... I had some 50 million build errors though (something related to Python) so some targets were skipped by bjam. -- http://eisenbits.homelinux.net/~stf/ OpenPGP: DFD9 0146 3794 9CF6 17EA D63F DBF5 8AA8 3B31 FE8A Like hardship, risk & challenge? --- Follow Jesus!!

2 1

boost::asio::io_service destructor never returns
by custgmx.net 17 Sep '10

17 Sep '10

Hello, he timer also starts a thread in which an io_service hosts deadline timer until thread is terminated. so a continuous timer. The boost thread which needs the timer is create from within DLL. The DLL ExitInstance function is called, when the hosting App. unloads the DLL. The ExitInstance function stops the thread and before timer. But the io_service destruction in my timer never returns, so the app hangs. This happens NOT, when i am able to call a Dispose Function before ExitInstance is called. However, some application loading my DLL, give not the chance to call this expose function. Anyone know, how to work around this problem ? Here is the code of my timer core. It is the thread which restarts the service until thread is stopped. The thread get's stopped by setting _stop flag and setting deadlime timer to 1 ms in future. summary: hangs when within Dll::ExitInstance destructed. Hangs not, if destrcuted before Dll::ExitInstance Thank you Code: void tcTimerThread::timerLoop(void) { _running=true; _io_service = new boost::asio::io_service; /// create timer _pTimer = new boost::asio::deadline_timer(*_io_service); while(_stop==false) { _pTimer->expires_from_now(boost::posix_time::milliseconds(_delay)); /// bind timer event function _pTimer->async_wait(boost::bind(&tcTimerThread::timerEvent,this,boost::asio: :placeholders::error)); try { if(_stop==false) { /// reset async _io_service->reset(); /// wait for timer event _io_service->run(); } } catch(...) { } } try { _io_service->stop(); delete _pTimer; /// !! never returns if called within ExitInstance of DLL;returns always is called before ExitInstance of DLL delete _io_service; } catch(...) { } _running=false; }

1 0

[process] Determine if a process is still running?
by Allen Cronce 17 Sep '10

17 Sep '10

Hi all, I'm interested in a cross platform way to determine if a process as identified by process ID is still running. There is no parent/child relationship between the running and detecting processes. However it is easy in my particular scenario for the running process to communicate its ID to the detecting process for later evaluation. I know that I can write separate Windows and Posix implementations that would work. But I'd prefer a cross-platform implementation rather than conditionally calling native API's. I can see that boost::process supports obtaining a process ID. The question is can boost::process use this ID to determine if a given process, which was not launched as a child, is still running? Thanks in advance for any suggestions. Best, -- Allen Cronce

5 7

Re: [Boost-users] boost::bond and assignment
by przemyslaw.sliwa＠uk.bnpparibas.com 17 Sep '10

17 Sep '10

Thanks for help, but I want to assign the value of the member variable not the pointer itself: vector<boost::shared_ptr<clss> > tmp for(size_t i=0; i<tmp.size(), i++) tmp[i]->mem = 0.0; In this case clss::mem should be changed, I get an error doing std::for_each(tmp.begin(), tmp.end(), &_1::mem = 0); Can this be done? Thanks for help ___________________________________________________________ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is prohibited. Please refer to http://www.bnpparibas.co.uk/en/information/legal_information.asp?Code=ECAS-… for additional disclosures.

2 1

boost::bond and assignment
by przemyslaw.sliwa＠uk.bnpparibas.com 17 Sep '10

17 Sep '10

Hello, I have to write a simple loop whihc assigns a member variable to a constant value, vector<boost::shared_ptr<clss> > tmp for(size_t i=0; i<tmp.size(), i++) tmp[i]->mem = 0.0; How this can be done using stl algorithms and boost::bind? Thanks for help, Pshemek ___________________________________________________________ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is prohibited. Please refer to http://www.bnpparibas.co.uk/en/information/legal_information.asp?Code=ECAS-… for additional disclosures.

2 1

Re: [Boost-users] [boost] Interest in B-tree library for Boost?
by Imre Palik 17 Sep '10

17 Sep '10

> From: Cory Nelson <phrosty(a)gmail.com> > - Can this be adapted for in-memory use as well, with full non-POD support? You mean cache-oblivious B-trees? That would be really cool. BTW, anybody has real world performance data on them? I.

1 0

[Mpl, Fusion] using adapted struct with mpl algorithms
by Paul Graphov 17 Sep '10

17 Sep '10

Hello Boost Users, I've encountered a trouble using fusion adapted struct as mpl sequence: when I call mpl::push_front with fusion::vector it works but if I try to call it with adapted struct, it fails. Do I miss something? Is there any concise solution or I have to convert it by hand? source: http://pastebin.com/3ELipu1M 1. #include <string> 2. 3. #include <boost/fusion/adapted/struct/adapt_struct.hpp> 4. #include <boost/fusion/mpl.hpp> 5. #include <boost/fusion/container/vector.hpp> 6. #include <boost/mpl/push_front.hpp> 7. 8. typedef boost::fusion::vector<std::string, int> employee_1; 9. 10. struct employee_2 11. { 12. std::string name; 13. int age; 14. }; 15. 16. BOOST_FUSION_ADAPT_STRUCT( 17. employee_2, 18. (std::string, name) 19. (int, age)) 20. 21. /* this line compiles just fine */ 22. typedef boost::mpl::push_front<employee_1, bool>::typebool_employee_1 ; 23. 24. /* this fails */ 25. typedef boost::mpl::push_front<employee_2, bool>::typebool_employee_2 ; 26. 27. int main() { 28. return 0; 29. } Thanks!

1 1

download question: file checksums
by Stanisław Findeisen 17 Sep '10

17 Sep '10

What are the checksums of the release files?? STF -------- Original Message -------- Subject: download question Date: Tue, 31 Aug 2010 13:36:04 +0200 From: Stanisław Findeisen <stf(a)eisenbits.homelinux.net> To: boost-users(a)lists.boost.org Hi What are the file checksums? -- http://eisenbits.homelinux.net/~stf/ OpenPGP: DFD9 0146 3794 9CF6 17EA D63F DBF5 8AA8 3B31 FE8A Like Hardship, Risk & Challenge? --- Follow Jesus!!

2 1