- Boost - lists.boost.org

Library for printing STL containers
by Eric Curtin 14 Apr '18

14 Apr '18

Hi Guys, I have tried to contact the developer of this neat little library. It allows you to use streams such as ostringstreams and couts with various STL containers, without the boilerplate of any loops to get all the contents. I will likely fork and maintain it as I have tried (and failed) to contact the developer. https://github.com/louisdx/cxx-prettyprint If I cleaned it up, could we consider it for boost inclusion? It is already under boost open source license.

2 1

MSVC now correctly reports __cplusplus
by degski 12 Apr '18

12 Apr '18

https://blogs.msdn.microsoft.com/vcblog/2018/04/09/msvc-now-correctly-repor… degski

1 0

[release] Boost 1.67.0 Release Candidate 1
by Daniel James 11 Apr '18

11 Apr '18

The release candidates for the 1.67.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.67.0/source/> The SHA256 checksums are as follows: 289d55fc90b637781018c4babe3ba83244175aa539b54bc687529a65e352e713 boost_1_67_0_rc1.7z 0d13e038f8f402ea0d811397876c8e6f2a2352c170f90d0a42bb61dcec3f86fc boost_1_67_0_rc1.tar.bz2 5d25d1cdf6f7061f25463f59ce2e5c9e1cecfece90d86a04513de386c86fbb5e boost_1_67_0_rc1.tar.gz ae8d461a8573d24813c92e3daf1f7832908d1845820d94b77243d6cd06197635 boost_1_67_0_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.

4 5

[build] Broken doc links
by Gavin Lambert 10 Apr '18

10 Apr '18

Prompted by the thread "Toolset version for Visual Studio 2017 15.6.3" over in the user list, I was looking through some Boost.Build documentation when I found some dead links and other weirdness. Boost.Build's github page links to https://www.boost.org/build/, which appears to be fully working. On https://www.boost.org/doc/libs/1_66_0/more/getting_started/windows.html, under "5.2.1 Install Boost.Build" it links to https://www.boost.org/doc/libs/1_66_0/tools/build/index.html, which appears to be a versioned clone of the above. But at that page, the "Documentation" link points at https://www.boost.org/doc/libs/1_66_0/tools/build/doc/html/index.html, which 404s. Back in "Getting Started", in "5.2.2 Identify Your Toolset" it first links directly to https://www.boost.org/build/doc/html/bbv2/reference/tools.html (which is now an unversioned link, but does work), and then to https://www.boost.org/doc/libs/1_66_0/doc/html/bbv2/installation.html (which is a versioned link that also works). So it's not very consistent. Putting these things together, it looks like the "right" root page for the versioned documentation should be https://www.boost.org/doc/libs/1_66_0/doc/html/bbv2.html, although that lacks some user-friendliness. (And it also links to https://www.boost.org/boost-build2 for yet another URL variation... although that does redirect to https://www.boost.org/build/ at least.)

2 2

please integrate patches for Boost.Gil and Boost.Graph
by Brook Milligan 10 Apr '18

10 Apr '18

I am not sure what the correct procedure for this is, but there are at least two old patches that would improve Boost.Gil and Boost.Graph. I would greatly appreciate it if someone integrates these. I have been using these for some time now with no detrimental effects. The patch to Boost.Gil corrects clearly incorrect code. The patch to Boost.Graph solves a problem that should never have been in the original design in the first place. Since it expands the acceptable set of arguments to cover the full range of values any user would expect and has the original semantics for cases that worked before, as far as I can see there can be no effect on existing user code. Thank you very much. Cheers, Brook See the following: - https://lists.boost.org/Archives/boost/2013/02/200721.php - https://svn.boost.org/trac10/ticket/7270 - https://svn.boost.org/trac10/ticket/9517 - https://svn.boost.org/trac10/attachment/ticket/9517/gil_channel_algorithm.p… - https://svn.boost.org/trac10/ticket/13397 --- boost/gil/channel_algorithm.hpp.orig 2018-02-23 22:45:42.000000000 -0700 +++ boost/gil/channel_algorithm.hpp 2018-03-11 22:05:31.000000000 -0600 @@ -25,6 +25,7 @@ #include "gil_config.hpp" #include "channel.hpp" +#include <limits> #include <boost/mpl/less.hpp> #include <boost/mpl/integral_c.hpp> #include <boost/mpl/greater.hpp> @@ -51,7 +52,7 @@ template <typename UnsignedIntegralChannel> -struct unsigned_integral_max_value : public mpl::integral_c<UnsignedIntegralChannel,-1> {}; +struct unsigned_integral_max_value : public mpl::integral_c<UnsignedIntegralChannel,std::numeric_limits<UnsignedIntegralChannel>::max()> {}; template <> struct unsigned_integral_max_value<uint8_t> : public mpl::integral_c<uint32_t,0xFF> {}; Allow dimensions to have length >= 1, rather than > 1. See https://svn.boost.org/trac10/ticket/11735. --- boost/graph/grid_graph.hpp.orig 2017-12-13 16:56:43.000000000 -0700 +++ boost/graph/grid_graph.hpp 2018-04-07 09:33:56.000000000 -0600 @@ -630,15 +630,17 @@ // If the vertex is on the edge of this dimension, then its // number of out edges is dependent upon whether the dimension - // wraps or not. - if ((vertex[dimension_index] == 0) || - (vertex[dimension_index] == (length(dimension_index) - 1))) { - out_edge_count += (wrapped(dimension_index) ? 2 : 1); - } - else { - // Next and previous edges, regardless or wrapping - out_edge_count += 2; - } + // wraps or not, but only if the length is > 1. + if (length(dimension_index) > 1) { + if ((vertex[dimension_index] == 0) || + (vertex[dimension_index] == (length(dimension_index) - 1))) { + out_edge_count += (wrapped(dimension_index) ? 2 : 1); + } + else { + // Next and previous edges, regardless or wrapping + out_edge_count += 2; + } + } } return (out_edge_count);

4 7

[concept_check] Reference page concept links out-of-date
by Spencer Collyer 09 Apr '18

09 Apr '18

Not sure if this has been reported before, but any links on the Reference page of the concept_check library that point to SGI.com now take you to a page that says 'SGI.com Tech Archive Resources now retired'. Regards, Spencer Collyer

5 4

Reducing dependencies
by Antony Polukhin 08 Apr '18

08 Apr '18

Hello, I've noted that many libraries depend on container_hash while it depends only on a single header from Boost.Detail library https://pdimov.github.io/boostdep-report/master/module-levels.html Can we move "boost/detail/container_fwd.hpp" into Boost.Core or into Boost.ContainerHash? This will break the circular dependency, move the Boost.ContainerHash on level 4 and improve levels of Intrusive, Container, CircularBuffer, Unordered, Algorithm, Test, TypeIndex, Any, Function, Functional, ScopeExit, Signals, MultiArray, Variant. -- Best regards, Antony Polukhin

6 12

[release] 1.67.0 mostly closed for release candidate
by Daniel James 07 Apr '18

07 Apr '18

The master branch is now closed for all changes except by permission for the release candidate. We're expecting potential fixes for build, context and a documentation update for ptr_container. Please let us know if there are any other fixes that you want to include in the release. Thanks, -- The Boost Release Team

5 9

mkmakefile
by Ggh 05 Apr '18

05 Apr '18

Hi! is anyone interested in developing this code further? pls have a look at: http://www.multi.fi/~ghaga http://www.multi.fi/~ghaga/mkmakefile/ anyone? Ty, Greg

4 6

[ptr_container] Docs not updated to reflect std::auto_ptr -> std:unique_ptr changes
by Edward Diener 04 Apr '18

04 Apr '18

An issue was recently created that while ptr_container now supports std::unique_ptr where appropriate and no longer supports std::auto_ptr where it has been removed from the C++ standard, the docs were never updated to reflect this change. I thought it would be worthwhile mentioning this as we go to the 1.67 release. A contributo is preparing a PR to correct this issue, and I will review as a member of CMT once the PR is submitted. I don't mean this as a way to delay the new release but I thought I should bring this up in the mailing list so others know this is the case.

2 1