- Boost - lists.boost.org

[release] 1.69.0 post-beta merges
by Marshall Clow 26 Nov '18

26 Nov '18

The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See < https://github.com/boostorg/boost/wiki/Release-Beta-Merge-Policy> The master branch will close for the 1.69.0 release on 5-December. The release calendar is at https://www.boost.org/development/index.html -- The Boost release team.

8 17

[release] 1.69.0 post-beta merges
by Oliver Kowalke 26 Nov '18

26 Nov '18

Hi, boost.context needs a post-beta merge in order to fix some issue on ELF asm. Do I get permission to merge to master? best, Oliver

2 1

Guidence on #pragma once
by Robert Ramey 25 Nov '18

25 Nov '18

In the safe numerics library my *.hpp files start with the following boiler plate: #ifndef BOOST_NUMERIC_AUTOMATIC_HPP #define BOOST_NUMERIC_AUTOMATIC_HPP // MS compatible compilers support #pragma once #if defined(_MSC_VER) && (_MSC_VER >= 1020) # pragma once #endif ... I would like to replace all this in every file with just #pragma once according to https://en.wikipedia.org/wiki/Pragma_once#cite_note-9 this should be possible while supporting almost all which claim to be C++ 14 conformant. The exception noted is C++ for Cray. I realize that strictly speaking I shouldn't do this. But it would instantaneously remove some cruft from my code as long as the occasional error from repeating the same include guard text in multiple files. It might have some performance benefits and some other repercussions related to pre-compiled headers. Who knows what else. It would be interesting to know what others might have to say about this. Robert Ramey

10 10

[Boost][DoubleEnded] Status?
by degski 25 Nov '18

25 Nov '18

We had the review of this library proposal/addition quite a while back and ever since I've been [eagerly] waiting for its official entry into Boost. https://github.com/erenon/double_ended does not show any activity and there is nothing in the Boost.Container going on either. What is the status? degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*

4 6

Geometry path length breaking windows regression runs
by Tom Kent 23 Nov '18

23 Nov '18

There has been a change to the geometry library, sometime around Nov 14, that is causing the windows regression runners I manage to crash. The issue is that it is creating *very* long filesystem paths, even with the regression --abbreviate-paths option set. There are a bunch of files such as: D:\teeks99-08\run\results\boost\bin.v2\libs\geometry\test\self_contained_headers\self-contained-algorithms-detail-buffer-buffered_piece_collection~hpp.test\msvc-14.1\dbg\adrs-mdl-64\async-excpt-on\thrd-mlt\self-contained-algorithms-detail-buffer-buffered_piece_collection~hpp.obj.rsp That seem to be created alright, but when I try to cleanup the run afterwards, windows doesn't allow me to delete the files. Tom

5 4

Help - my disk is full! (of bin.v2 stuff)
by Paul A. Bristow 21 Nov '18

21 Nov '18

I note with surprise (and alarm) that my Boost-stuff disk partition is nearly full! Closer inspection reveals that I have a bin.v2 folder of over 50 GB. Obviously, I need to delete something. What are the implications of deleting things? What is the best option? Should I simply delete the whole folder bin.v2 (I have, in desperation, gone nuclear some time ago) or just bin/v2/libs or ? Expert advice welcome. Thanks Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

5 4

Rotating on-call review managers
by Zach Laine 19 Nov '18

19 Nov '18

Boost was originally created to incubate libraries that target eventual standardization. When new libraries are proposed, many of the Boost community members that participate in C++ Standard Committee (WG21) meetings ask "How many users does this have, and did you consider Boost first?" Often the answer is that they considered Boost but could not figure out what they were supposed to do to make that happen, or that they had difficulty finding a review manager. There are other things that can be done to make getting a library Boost-review-ready, but most of them require a bit of work up front. The review manager requirement is relatively easier to satisfy. This volunteer effort is to better facilitate Boost's value in the ISO C++ standardization process and so the reviewers would need to recognize intent to standardize the proposed libraries. Submissions that are supported with a paper in a mailing or a draft will make it easier to source a review manager from this queue, but authors without either are encouraged to get in contact with reviewers on this list to find out what that entails. This is the list of volunteers: Zach Laine Micheal Caisse Matt Calabrese Louis Dionne Vinnie Falco Glen Fernandes Jeff Garland David Sankel The list will rotate; the first person on the list will be "on-call". If you'd like to help, let me know and I'll add your name to the list. Also, I've made a PR that adds this list and a note like the description above to https://www.boost.org/development/submissions.html (#6 Seek a Review Manager): https://github.com/boostorg/website/pull/387 Zach

2 2

[release] Boost 1.69.0 Beta 1 Release Candidate 1
by Marshall Clow 19 Nov '18

19 Nov '18

The release candidates for the first 1.69.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.69.0.beta.1.rc1/source/> The release notes are not yet available. The updated documentation is not yet available. [ They will be available in a day or two. ] The SHA256 checksums are as follows: db6b346389714647490d6503db881e4178dd8cd498f850999bebf72cacd4c4ed boost_1_69_0_b1_rc1.7z d128c82351becbd37a02b9b4818994d3f66ff8bdbc0a18838206f4c070db97af boost_1_69_0_b1_rc1.tar.bz2 4df6262db53cfd0d0f934cb126f7e48e94872fe4441cbac6bf72a43bfb136a45 boost_1_69_0_b1_rc1.tar.gz e2908e33cc15f92cda06ddde6a3da43b18967a83105355571fc3cf6e75820c7f boost_1_69_0_b1_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. -- The Boost Release Managers

6 17

[release] Boost 1.69.0 Beta 1
by Marshall Clow 19 Nov '18

19 Nov '18

Boost release 1.69.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.69.0.beta1/source/> The SHA256 checksums are as follows: ee0ecd7d31f58474c1e0210089c9e66bd878d4d1e7436ac511e359aa4a9d3e86 ./boost_1_69_0_b1.7z 3e25c46f2171799caabbeb419ba7859fffb62208f3a1c80798713377ab07af0e ./boost_1_69_0_b1.tar.bz2 71f4b57175058af1b8c320971cf29226e5a652931a679f7e1c086655147ecafb ./boost_1_69_0_b1.tar.gz ec9ef7d2c9f0d41f560769e67bc7ff207cc999243a7dd6c3f6bcfbdbf0827a7b ./boost_1_69_0_b1.zip For details of what's in the release, see < https://www.boost.org/users/history/version_1_69_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

`b2 toolset=clang-win` now works on Appveyor
by Peter Dimov 18 Nov '18

18 Nov '18

With the current develop branch (since Boost.Build hasn't been merged to master yet), b2 toolset=clang-win now works on Appveyor without additional configuration. You can see it in action at https://ci.appveyor.com/project/pdimov/assert/builds/20331077/job/0hux9a6ml…

4 16