- Boost - lists.preview.boost.org

[regex][config] BOOST_FALLTHROUGH not on the release branch
by Daniel James 26 May '13

26 May '13

The implementation of the new BOOST_FALLTHROUGH macro hasn't been merged to release yet, but the regex merge from yesterday included some code which uses it, so that isn't compiling now. The test results are a bit behind, so it hasn't shown up there yet.

2 2

Boost.Thread Co-authoring
by Vicente J. Botet Escriba 26 May '13

26 May '13

Hi, I'm the main maintainer of Boost.Thread since Nov 2011. I've fixed a lot of bugs and added a lot of new features (mainly conformance with C++11, but also others). Could my name appear as co-author of Boost.Thread in http://www.boost.org/doc/libs/1_53_0/? Best, Vicente

4 3

[trac] New component for type_erasure.
by Daniel James 25 May '13

25 May '13

Please can someone create a component for 'type_erasure', user 'steven_watanabe'? Thanks.

2 1

[bind][function][lamda][signals][variant][boostbook] PDF doc builds broken?
by John Maddock 25 May '13

25 May '13

The libs bind, lambda, signals, variant and boostbook all have: project boost/doc ; In their Jamfiles, and Boost.Build is now treating that duplication as an error. Is there any reason these project ID's can't be just commented out / removed? Thanks, John.

3 3

[multi-array] warning on mingw caused by assert macro
by Ronan Trépos 24 May '13

24 May '13

Hello boost comunity, I found a warning using boost/multi-array (boost 1.53) on mingw. The warning message : boost/multi_array/base.hpp:503:13: attention : unused variable 'bound_adjustment' When compiling a simple example including muti-array with the command line : c:\MinGW\bin\g++.exe -Wall -Wextra -O2 -DNDEBUG -g -Ic:/natifvle/install/boost/include/boost-1_53 -o MyExample.o -c MyExample.cpp The reason is that a locale variable bound_adjustement, before line 503 of multi_array/base.hpp, is defined and computed only if BOOST_DISABLE_ASSERT is not set. The line after, a BOOST_ASSERT is called using bound_adjustement. Since BOOST_DISABLE_ASSERT is not set, BOOST_ASSERT is defined as the mingw macro "assert" in boost/assert.hpp. Finally, mingw assert macro (see Mingw/include/assert.h) is defined as ((void) 0) if NDEBUG is defined (this is the case in my example). It took me a long time to see the problem. So my questions are : - Do I miss use the combination of NDEBUG and BOOST_DISABLE_ASSERTS ? Eg. if NDEBUG and BOOST_DISABLE_ASSERTS are set (or unset) together, then I have no warning. Should they be set to the same value ? - Or should boost/assert.hpp take into account NDEBUG for defining the macro BOOST_ASSERT (only for mingw ?) Best regards Ronan Trépos -- Trépos Ronan INRA unité MIAT, équipe RECORD, Toulouse http://carlit.toulouse.inra.fr/wikiz/index.php/Ronan_TREPOS tel : 05 61 28 51 89

1 0

[ASIO] Issue with epoll reactor? Callback handler not executed.
by Arpan Sen 24 May '13

24 May '13

Hi folks, I am using the latest version of Boost ASIO on a Suse11 box. I recently upgraded from an older version of Boost, and life since then has been unusually harsh. **** I have a piece of ASIO code that worked just fine earlier but doesn't do so now. Here's the offending snippet, rather simple looking: **** boost::asio::streambuf response; ... // code for deadline timer tcp::socket socket(io_service); socket.async_connect(*iterator, &conn_handler); io_service.reset(); io_service.run_one(); async_write(socket, buffer(command.c_str()), &write_handler); io_service.reset(); io_service.run_one(); async_read_until(socket, response, '\n', &read_handler); io_service.reset(); io_service.run_one(); Everything works fine till async_write. During async_read_until I can see that the response buffer does have some data by the time it returns. However, when io_service.run_one() happens the read_handler is NOT ALWAYS called which is very surprising. The function calling the read_handler (internal to ASIO) also does a commit to the streambuf so streambuf.size() becomes non-zero, i.e. ready for consumption by something like istream. All of that is missing now. Debugging this in some detail, I see that run_one is in fact responsible for calling read_handler. That is NOT happening and in epoll_reactor I am not seeing any real activity. Something there is activity and the behavior is as expected but 9/10 times completion handler won’t be called. The io_service object runs in a specific thread (I have a bunch of threads in my app) and no other thread accesses it. The Linux kernel running previous version has not been changed when I upgraded the Boost libraries. Instead of epoll, if I use select everything looks good. Any thoughts? Arpan

2 1

[git][property_tree] Conversion Looks Good, Lots of Redundant Branches
by Sebastian Redl 24 May '13

24 May '13

Reviewed the PropertyTree git history. Apart from the existence of all these redundant branches it looks good. Is there a way to modify the conversion script so that the branch commit itself doesn't show up if there are no follow-ups? Not a big thing, I can easily kill those branches afterwards, but they look so useless. Sebastian

2 1

[githelp] modular boost instructions?
by legalize+jeeves＠mail.xmission.com 24 May '13

24 May '13

[Please do not mail me a copy of your followup] OK, we've already established that the 'Experimenting with Modular Boost' instructions are woefully stale. Can someone please briefly describe what submodules I need to manually add just to get something bootstrapped? In the svn boost there is <root>/build and <root>/tools/build; neither of these is present in boostorg/boost and while there is a build repo, it seems to define a structure that creates <root>/build/build, so I'm confused. -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>

9 32

[thread] SEVERE bug on packaged_task constructor in C++11 mode.
by Vicente J. Botet Escriba 23 May '13

23 May '13

Hi, There is a severe bug in packaged_task constructor when compiling in C++11 mode and giving a copyable functor as parameter, as reported in https://svn.boost.org/trac/boost/ticket/8596. I believe that this is not a regression, this have never worked. Until I find a fix, the packaged_task could be used only with free functions and with movable functors when compiling in C++11 mode. Fortunately there is no regression on C++98 compilers (at least not identified yet). Sorry for the disagreement, Vicente

3 5

[circular_buffer] Volunteer(s) needed
by Jan Gaspar 23 May '13

23 May '13

Hi all, Is there any volunteer that could take over the circular_buffer library? I do not maintain it any more. There are several bugs which need to be fixed and one challenging feature request (to implement move semantics). Here is the full list: Type: Bugs #4100 some boost classes have sizeof that depends on NDEBUG #5362 circular_buffer does not compile with BOOST_NO_EXCEPTIONS #6277 Checked iterators are not threadsafe #6747 Circular_Buffer / Bounded_Buffer inside Template class problem #7025 circular buffer reports warning: " type qualifiers ignored on function return type" while compile. #7950 Eliminate W4-warnings under VS2005 #8012 Inconsistency in linearize() #8438 vector & circular_buffer storage misbehave when using compiler optimizations Type: Feature Requests #5511 Documentation needs some improvement #7888 circular_buffer should support move semantics Type: Patches #8032 Warning fixes in circular_buffer (Prior doing any changes please read how the circular_buffers' documentation is generated: http://svn.boost.org/svn/boost/trunk/libs/circular_buffer/doc/HOWTO-srcdoc) Thanks and regards, Jan

6 13