November 2016 - Boost - lists.preview.boost.org

[filesystem] Move constructor from string_type
by danny kabrane 03 Nov '16

03 Nov '16

Hi all, boost::filesystem::path has 2 constructors from a string_type, one with a const reference and another one without const (wich I find troubling), but there's no constructor from a rvalue string_type. Is there something planned to add a move constructor from a string_type ? Regards Danny

2 1

[build] Annoying warnings from Asio, -isystem from bjam?
by Vinnie Falco 02 Nov '16

02 Nov '16

When I have "-Wunused-variable" I get these highly annoying warnings from boost/asio/error.hpp which I'm sure almost everyone has seen: boost_1_60_0/boost/asio/error.hpp:258:45: warning: ‘boost::asio::error::system_category’ defined but not used [-Wunused-variable] static const boost::system::error_category& system_category I don't want to disable the warning but I also don't want the false positives. Thankfully, clang and gcc have this wonderful option "-isystem" which lets you mark include paths as belonging to the system. This prevents warnings from being emitted that the programmer can do nothing about. How can I get Boost.Build to add the Boost library header search paths using "-isystem" so that gcc doesn't report warnings in Boost headers that I cannot do anything about? More detail here: http://stackoverflow.com/questions/1867065/how-to-suppress-gcc-warnings-fro… I've played around with <sysinclude> but can't seem to figure it out. Here's my Jamroot (my project builds on its own, without putting it in the Boost tree): https://github.com/vinniefalco/Beast/blob/master/Jamroot#L80 -- Follow me on Github: https://github.com/vinniefalco

2 2

[algorithm]Interface for search algorithms
by Зайцев Александр 02 Nov '16

02 Nov '16

1 0

[release] 1.63.0 closed for major changes
by Daniel James 02 Nov '16

02 Nov '16

Hi, The master branch is closed for major changes. In one week (9th Nov) it will be closing for the beta release. The full schedule is on the website: http://www.boost.org/development/ And if you haven't done so yet, please can you add your libraries' details to the release notes at: https://github.com/boostorg/website/blob/master/feed/history/boost_1_63_0.q… Or email them to me, if you don't like writing quickbook.

1 0

Curiousity question
by Edward Diener 01 Nov '16

01 Nov '16

I would like to ask a design question for any Boost developers or anyone on this mailing list who might care to answer. You are designing or working on a library, perhaps for Boost, perhaps for fun, and part of the design of the library has some public functionality taking a shared pointer as input. You: 1) Use boost::shared_ptr 2) Use std::shared_ptr 3) Use both boost::shared_ptr and std::shared_ptr with the same functionality 4) Use neither, you roll your own shared pointer-like functionality 5) You don't lke shared pointers and use raw pointers instead I really am curious about this. I haven't put any limitation on your library or made any presumption on who your library is for, on purpose. Thanks for anyone answering !

13 53