December 2017 - Boost - lists.boost.org

[date_time] Trac 13194 - %e posix time_input_facet specifier behavior
by James E. King, III 21 Dec '17

21 Dec '17

https://svn.boost.org/trac10/ticket/13194 Just looking at this one, and looking at the documentation, it states that %e is the same as %d however when the value is less than 10, a leading space is to be used instead of a leading zero. The example in the description has a flaw, I believe, and I commented on that. Do folks agree with my comment? Should parsing fail if it says "December 5" (with one space) and the format string is "%B %e"? Valid input would be "December 5" (with two spaces). I also found that the code blindly ignores delimiter specifiers, so I opened a github issue for it: https://github.com/boostorg/date_time/issues/53. Comments appreciated there as well. Thanks, Jim

2 2

[endian] undefined behaviour in boost.endian
by Arvid Norberg 21 Dec '17

21 Dec '17

Hi, I've submitted an issue to the github project for boost.endian. I'm starting to wonder if this is in fact not the preferred channel for reporting issues. There are at least two separate issues causing undefined behaviour to be invoked in boost.endian. The first one is fundamentally based on the assumption that if the target architecture is x86, the C++ alignment requirements don't apply. I've posted more details here: https://github.com/boostorg/endian/issues/21 with a proposed patch here: https://github.com/boostorg/endian/pull/22 The second issue involves shifting negative integers, both invoking implementation defined and undefined behaviour. I don't have a patch to fix the issue, just to extend the tests to exercise the problem, which is then detectible with the undefined behaviour sanitizer. Patch is here: https://github.com/boostorg/endian/pull/24 I would really appreciate it if someone could review these and/or suggest a better venue than github to propose patches. thanks! -- Arvid Norberg

3 2

[build] Currently broken with Xcode 8?
by John Maddock 20 Dec '17

20 Dec '17

Current develop appears not to build with XCode 8.0 causing Travis tests to fail, for example: https://travis-ci.org/boostorg/config/jobs/318188889 Thanks, John. --- This email has been checked for viruses by AVG. http://www.avg.com

5 6

[release] Boost 1.66.0
by Daniel James 19 Dec '17

19 Dec '17

Release 1.66.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains N new libraries and numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.66.0> You can also download directly from: <https://dl.bintray.com/boostorg/release/1.66.0/> To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. Thanks, -- The Boost Release Team Vladimir Prus, Marshall Clow, Eric Niebler, Daniel James, Beman Dawes

2 1

[release] 1.67.0 open for merging
by Daniel James 19 Dec '17

19 Dec '17

The master branch is open for merging all stable changes from develop, including bug fixes and major upgrades to existing libraries. Breaking changes should be coordinated via the mailing list with the developers of the other libraries affected. New libraries may be added, but require permission of a release manager. In other words, merging does not require permission from a release manager, except for new libraries. Boost Calendar with the release schedule: http://www.boost.org/development/index.html Release schedule explanation: https://github.com/boostorg/boost/wiki/Release-Schedule Release practices for developers: http://svn.boost.org/trac/boost/wiki/ImprovingPractices -- The Boost Release Team

1 0

[release] 1.66.0 post-beta merges
by Daniel James 19 Dec '17

19 Dec '17

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>

14 32

[release] Boost 1.66.0 Release Candidate 2
by Daniel James 18 Dec '17

18 Dec '17

The second release candidates for the 1.66.0 release are now available at: <https://dl.bintray.com/boostorg/prerelease/> The in progress release notes are: <http://www.boost.org/users/history/in_progress.html> Library documentation is available at: <http://www.boost.org/doc/libs/1_66_0/> The SHA256 checksums are as follows: 596389389c005814ecb2a6b64c31dccd2c3e6fbc5a802b4dfada999ae5844628 boost_1_66_0_rc2.7z 5721818253e6a0989583192f96782c4a98eb6204965316df9f5ad75819225ca9 boost_1_66_0_rc2.tar.bz2 bd0df411efd9a585e5a2212275f8762079fed8842264954675a4fddc46cfcf60 boost_1_66_0_rc2.tar.gz e1c55ebb00886c1a96528e4024be98a38b815115f62ecfe878fcf587ba715aad boost_1_66_0_rc2.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.

12 31

boost-1.66.0 tag?
by James E. King, III 18 Dec '17

18 Dec '17

I just refreshed Boost.Uuid locally and don't see a boost-1.66.0 tag. I had assumed this would be added by the upstream build and release procedure? Am I supposed to make that tag? - Jim

2 2

[chrono][timer][release] Non-inline functions in inlined headers
by Daniel James 14 Dec '17

14 Dec '17

Hi, We've had a link problem reported. for this code on Visual Studio, using auto-linking: #include "boost\chrono.hpp" #include "boost\timer\timer.hpp" int main() { auto now = boost::chrono::steady_clock::now(); boost::timer::cpu_timer cput; return 0; } I haven't got the binaries installed yet, so I haven't reproduced it, but I think it's caused because timer now includes the chrono headers using BOOST_CHRONO_HEADER_ONLY, and in the chrono inlined headers not all functions are BOOST_CHRONO_INLINE. It looks like this problem was always in chrono, but BOOST_CHRONO_HEADER_ONLY was widely used enough for it to be detected. I'd quite like to fix this for 1.66.0, which requires either reverting the change to timer, or fixing the problem in chrono. The error is in chrono, but I'm more inclined to revert the change in timer for this release, as it's a less disruptive way of quickly fixing the problem. https://github.com/boostorg/timer/pull/5

3 8

Building only x86 /MDd and /MT on msvc 2017
by Fredrik Stax{ng 13 Dec '17

13 Dec '17

The docs says For instructions on how to build only specific variants, please ask on the Boost.Build mailing list. but I gmane gives a 411 for Boost.Build so I ask the question here. For 1.60.0 I used this cd modular-boost rem call .\bootstrap .\b2 headers .\b2 toolset=msvc variant=debug address-model=32 link=static threading=multi runtime-link=shared .\b2 toolset=msvc variant=release address-model=32 link=static threading=multi runtime-link=static Has this changed? -- Fredrik Stax\"ang | rot13: sfgk(a)hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET

1 0