August 2013 - Boost - lists.boost.org

boost::lockfree::spsc_queue and destructors
by Taylor Holliday 03 Aug '13

03 Aug '13

Hey Boost, I was passing some shared_ptrs between threads using a boost::lockfree::spsc_queue and it would seem that the shared_ptr destructor isn't called upon popping from the queue. So spsc_queue differs from a typical queue in that regard. Why is that? thanks! - Taylor

2 1

[git-help] New libraries?
by Rene Rivera 03 Aug '13

03 Aug '13

Today I checked in the new Predef library and I'm wondering, not just for it but in general, if this interim period of svn to git transition what happens to new libraries? Will they automatically show up in the git repos? What are the procedures if the new library is already, originally in git and modularized? Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

3 5

Reboot of the boost server machine
by DongInn Kim 02 Aug '13

02 Aug '13

Dear All, For the system maintenance, we need to reboot the following server machines today. I am sorry for such a short notice. - milliways - eddie - wowbagger (Boost websites and mailing lists) - deep-thought (NFS server) Date: Aug 2, 2013 Time: 4:00pm-4:30pm (E.T.) - 1:00pm-1:30pm Pacific US time - 2:00pm-2:30pm Mountain US time - 3:00pm-3:30pm Central US time - 4:00pm-4:30pm Eastern US time - 8:00pm-8:30pm GMT The following services would not be available during the system maintenance. - Web services (e.g., www.boost.org) - Subversion (e.g., svn.boost.org) - mailing lists (e.g., boost(a)lists.boost.org, …) - Login to the NFS $HOME mounted system - Mail archives - Send mail - NFS Please let me know if you have any issues or questions about this sudden reboot. Regards, -- - DongInn

1 0

Suppressing boost.thread and boost.system symbols in shared library
by Philip Bennefall 02 Aug '13

02 Aug '13

Hi all, I am building a shared library for Linux, for which I would like to export as few symbols as possible (ideally only the functions that my library users actually need to call). When building my project, I have the following options: -fvisibility=hidden -fvisibility-inlines-hidden I then mark all the functions that I am exporting as having default visibility. I link to static versions of boost.thread and boost.system. When I then say: nm -DC libtest.so I get a large number of symbols such as: 0002abe0 V typeinfo name for boost::exception_detail::clone_impl<boost::exceptio n_detail::bad_exception_> 0002ace0 V typeinfo name for boost::exception_detail::bad_exception_ 00029920 V typeinfo name for boost::exception_detail::error_info_injector<boost: :lock_error> 00029b00 V typeinfo name for boost::exception_detail::error_info_injector<boost: :condition_error> 00029860 V typeinfo name for boost::exception_detail::error_info_injector<boost: :thread_resource_error> 0002970f V typeinfo name for boost::thread_exception 00029a7b V typeinfo name for boost::thread_interrupted 00029740 V typeinfo name for boost::thread_resource_error 0002ac40 V typeinfo name for boost::enable_shared_from_this<boost::detail::threa d_data_base> 0002a720 V typeinfo name for boost::detail::thread_data_base 0002ad20 V typeinfo name for boost::detail::sp_counted_impl_p<boost::detail::thr ead_data_base> 0002adc0 V typeinfo name for boost::detail::sp_counted_impl_p<boost::exception_d etail::clone_impl<boost::exception_detail::bad_alloc_> > 0002ad60 V typeinfo name for boost::detail::sp_counted_impl_p<boost::exception_d etail::clone_impl<boost::exception_detail::bad_exception_> > 000296f1 V typeinfo name for boost::system::system_error I see this after having stripped the binary. Is there any way to get rid of these? Do I need to build Boost with some special cxxflags? Kind regards, Philip Bennefall

3 6

[predef] FYI..
by Rene Rivera 01 Aug '13

01 Aug '13

FYI.. to those that care.. I checked in changes to SVN to inject the Predef library into Boost. I say inject because the source is not actually in the SVN repo, it's external and still in github. But is being brought in through their SVN interface. Some testers have already runs the tests for it.. And at some point to be determined with some coordination with the community I will switch the "boost/detail/endian.hpp" header to point to the Predef compatibility equivalent... I suspect at the earliest one more week for that assuming no problems surface. Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

6 10

[predef] A few questions
by Andrey Semashev 01 Aug '13

01 Aug '13

Hi, I have a few questions/nitpicks regarding Boost.Predef: - I see that all headers have extension .h. Why is it not .hpp, like with the rest of Boost? It this intentional? - There is a tab in predef/version_number.h. There are also tabs in tests. - There are __SunOS_5_10, __SunOS_5_11 and similar macros defined on Solaris, which allow to detect OS version. These are not always available but I think SunPro defines them. Could these macros be used to select the proper OS version? - If I'm not mistaken, BOOST_COMP_GNUC and BOOST_COMP_MSVC will get defined not only for the real GCC and MSVC but also for pretenders. Is this intentional? If so, could we have special macros to detect these particular compilers? Boost.Config defines BOOST_MSVC and BOOST_GCC for this purpose. - There is considerable overlap with Boost.Config. Is there any plan to reduce the duplication? Maybe move some things from Boost.Config to Boost.Predef?

3 2

[boost.thread] Trouble building with MinGw 4.7.0
by Philip Bennefall 01 Aug '13

01 Aug '13

Hi all, Up until now I have been developing exclusively with VC++ 2010, and there my project builds just fine and without warnings. However, I am also planning to target Unix so I figured that a first step would be to make sure my project builds with MinGw. I set up my path environment variable to include the location of the MinGw 4.7.0 bin directory, and I built Boost with the following parameters: b2 variant=release link=static runtime-link=static threading=multi toolset=gcc Everything seems to be working fine (stage/lib contains all the .a files that I would expect). However, when I attempt to build my program I get tons of errors like the following: myprog_main.o:myprog_main.cpp:(.text+0x28ef): undefined reference to `__imp___ZN5boost6thread9interruptEv' myprog_main.o:myprog_main.cpp:(.text+0x294f): undefined reference to `__imp___ZNK5boost6thread6get_idEv' myprog_main.o:myprog_main.cpp:(.text+0x295d): undefined reference to `__imp___ZN5boost11this_thread6get_idEv' myprog_main.o:myprog_main.cpp:(.text+0x2973): undefined reference to `__imp___ZN5boost6thread13join_noexceptEv' myprog_main.o:myprog_main.cpp:(.text+0x2981): undefined reference to `__imp___ZN5boost6thread6detachEv' myprog_main.o:myprog_main.cpp:(.text+0x4600): undefined reference to `__imp___ZN5boost11this_thread18interruptible_waitEPvNS_6detail7timeoutE' myprog_main.o:myprog_main.cpp:(.text+0x49c2): undefined reference to `__imp___ZN5boost11this_thread18interruptible_waitEPvNS_6detail7timeoutE' myprog_main.o:myprog_main.cpp:(.text+0x667e): undefined reference to `__imp___ZN5boost11this_thread18interruptible_waitEPvNS_6detail7timeoutE' myprog_main.o:myprog_main.cpp:(.text+0x90a9): undefined reference to `__imp___ZN5boost6thread21start_thread_noexceptEv' myprog_main.o:myprog_main.cpp:(.text+0x9134): undefined reference to `__imp___ZN5boost6thread21start_thread_noexceptEv' myprog_main.o:myprog_main.cpp:(.text+0x917e): undefined reference to `__imp___ZN5boost6thread9interruptEv' myprog_main.o:myprog_main.cpp:(.text$_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvPFvPN5myprog5themeEENS2_5list1INS2_5valueIS6_EEEEEEED1Ev[boost::detail::thread_data<boost::_bi::bind_t<void, void (*)(myprog::theme*), boost::_bi::list1<boost::_bi::value<myprog::theme*> > > >::~thread_data()]+0x7): undefined reference to `__imp___ZN5boost6detail16thread_data_baseD2Ev' myprog_main.o:myprog_main.cpp:(.text$_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvPFvPN5myprog5themeEENS2_5list1INS2_5valueIS6_EEEEEEED0Ev[boost::detail::thread_data<boost::_bi::bind_t<void, void (*)(myprog::theme*), boost::_bi::list1<boost::_bi::value<myprog::theme*> > > >::~thread_data()]+0xe): undefined reference to `__imp___ZN5boost6detail16thread_data_baseD2Ev' myprog_main.o:myprog_main.cpp:(.text$_ZN5boost6threadD1Ev[boost::thread::~thread()]+0x9): undefined reference to `__imp___ZN5boost6thread6detachEv' Etc... I tried to specify -DBOOST_NO_LIB and add all the libraries manually, but no luck. Then I thought that maybe there's a problem with the fact that there are spaces in some of my directory names, so I copied the relevant .a files to the same directory as the program itself but still with no success. At this point, I'm swamped. I have managed to compile MinGw programs in the past that used Boost Thread, so I have no idea why it is not working with this version of Boost. Any suggestions would be highly appreciated. Kind regards, Philip Bennefall

2 5

Re: [boost] [multimethods] Proposal: Open Multi-Methods
by Daryle Walker 01 Aug '13

01 Aug '13

//================================================================= From: Jean-Louis Leroy Sent: ‎Saturday‎, ‎July‎ ‎27‎, ‎2013 ‎8‎:‎26‎ ‎PM I am working on library that pretty much implements what Pirkelbauer, Solodkyy and Stroustrup describe in their paper "Open Multi-Methods for C++" - although there are some divergences. I have posted it on GitHub: https://github.com/jll63/multimethods. Please examine the files in the "examples" directory to get an idea of how to use it. [SNIP] The library is essentially feature complete (if anything ever is). I am now going to work on the documentation, a build system, some clean up and compatibility (I tested it only with g++ 4.7.2 only so far). Is there interest in the Boost community for this stuff? If yes, I will adapt it to the guidelines and submit it for formal review. Of course, suggestions are welcome. //================================================================= Are virtual base classes supported? Maybe “virtual_” should be renamed to “virtualize” or “virtualized,” to avoid having a trailing underscore in a non-member name. A good way to document is to write a Doxygen comment as you write your class, function, or macro prototype. It makes you have to think about what the public side of your code has to do. But looking at your “next.cpp” example, you should start with documenting the “selector,” “virtual_,” “MM_CLASS,” “MM_INIT,” “MULTIMETHOD,” “BEGIN_METHOD,” “END_METHOD,” and “initialize” items. Anything in your implementation classes that don’t have to be seen by public code can be make private. Non-public types can go in a detail namespace. Daryle W.

3 2