December 2018 - Boost - lists.preview.boost.org

[docs] Building docs for release?
by John Maddock 15 Dec '18

15 Dec '18

Is there now a way for quickbook docs that aren't integrated under /doc/ to be built automatically for each release? And if so, what's the magic incantation to test this? Many thanks! John. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

Windows quarantines boost_1_68_0.7z
by Miguel Ojeda 15 Dec '18

15 Dec '18

Quick note: it seems that Windows currently quarantines boost_1_68_0.7z. Could someone from Boost please contact Microsoft to whitelist it? Thanks, Miguel

5 11

C++Now (BoostCon) 2019 Call for Submissions
by Jon Kalb 14 Dec '18

14 Dec '18

The C++Now (formerly BoostCon) 2019 Call for Submissions is now open. http://cppnow.org/announcements/2018/12/2019-call-for-submissions/ C++Now will be held in Aspen, Colorado on May 5th - 10th. Colorado has become trendy for C++ conferences, but BoostCon was here first. If you are interested in Boost Libraries and have never attended C++Now, you owe it to yourself to have the BoostCon experience. The best way to get your company to send you is to have an accepted submission. The deadline is early in the new year, so don’t delay. Jon Kalb Conference Chair C++Now

1 0

Let's discuss dropping support for msvc <= 9.0 (2008), gcc < 4.6, clang < 3.4
by James E. King III 13 Dec '18

13 Dec '18

During the Boost 1.69.0 release there was a regression on Visual Studio 2005 (msvc-8.0). Microsoft ended support for msvc-8.0 on December 4, 2016. I was going to argue we let it happen, but it wasn't the right time to discuss that sort of change. Boost has a very large compatibility matrix which increases the effort required, and sometimes limits solutions development, to get out a quality release. The boost project as a whole agreed in summer 2018 that if repository maintainers wanted to drop C++03 support per repository to make substantial improvements or simplifications, or to ease maintenance then they are able to do so. *Folks who need support for older language levels and older compilers can always download an older version of Boost.* The compilers I mentioned in the subject have trouble with C++11 and are no longer maintained. msvc-8.0 (Visual Studio 2005) ended support Dec 10 2016 msvc-9.0 (Visual Studio 2018) ended support April 10 2018 The last release of gcc 4.6 was April 12, 2013 The last release of gcc 4.5 was July 02, 2012 The last release of gcc 4.4 was March 13, 2012 The compilers by default in Ubuntu Trusty 14.04.5 LTS, supported through April 2019, is gcc-4.8, currently at gcc-4.8.2, and clang 3.4 (however clang-3.8 is available). My argument is that this is a huge project, and maintaining backwards compatibility is not always efficiently possible. We spend build matrix resources testing and analyzing those tests. We find and develop fixes and workarounds. In some cases we hobble potential solutions to cater to decade-old compilers. Given the summer 2018 discussions about language level, and the aging vendor support matrix, I'd like us to consider dropping support for msvc <= 9.0 (2008), gcc < 4.6, clang < 3.4. What does this mean exactly? 1. We no longer test these compilers in the post-commit build matrix. 2. We no longer test these compilers in continuous integration. 3. We no longer develop fixes for issues that affect these compilers. 4. We are allowed, over time, to remove workarounds for these compilers. 5. We no longer block releases due to incompatibility with these compilers. 6. We remove these compilers from the documented environments in the release notes. 7. We direct anyone looking for support of these compilers to download a previous release of Boost that given them that support. 8. We do not update older Boost releases to fix issues with older compiler support. What would we remove from the release notes as a result? primary: linux: clang: c++03: 3.0 c++0x: 3.0 c++11: 3.0, 3.1, 3.2, 3.3 gcc: c++03: 4.4.7, 4.5.3 c++0x: 4.4.7 windows: gcc: c++03: 3.4.5, 4.1.2, 4.2.4, 4.3.3, 4.4.0, 4.5.4 msvc: - msvc-7.0 (Visual C++ 7.1) - msvc-8.0 (Visual Studio 2005) - msvc-9.0 (Visual Studio 2008) additional: linux: clang: c++03: 3.0, 3.8.1, 3.9.1, 4.0.1 c++0x: 3.0 c++11: 3.0, 3.1, 3.2, 3.3 gcc: c++03: 4.4.7, 4.5.3 c++0x: 4.4.7 windows: gcc: c++03: 3.4.5, 4.1.2, 4.2.4, 4.3.3, 4.4.0, 4.5.4 msvc: - msvc-7.0 (Visual C++ 7.1) - msvc-8.0 (Visual Studio 2005) - msvc-9.0 (Visual Studio 2008) The release notes section on compiler compatibility should probably be updated to match the current state of the post-commit matrix and duplicates in the "additional" section that are present in the "primary" section should be removed, or simply merge them. Why do we have a distinction here? Thanks for your consideration, Jim

12 16

Is disabling boost log auto flush the only way to control the log flush? Or can you change log auto flush rate?
by hh h 13 Dec '18

13 Dec '18

Hi, I use boost log in an embedded system where flushing log message to flash storage need be controlled. I could not find how to change log auto flush rate, is it the only way to disable auto flush boost::log::keywords::auto_flush = false? I think there must be a way to change a desired log flush rate value without disabling auto flush, appreciate any tips. Thank you. JHH

2 2

[coroutine] Boost.Coroutine 1.0 Deprecation Warning
by Vinnie Falco 13 Dec '18

13 Dec '18

Can we please turn off this deprecation warning for now? At least when Boost.Coroutine is being included to work with Asio? I get neverending complaints from users about this warning in Beast: <https://travis-ci.org/vinniefalco/beast/jobs/466272022#L1091> I am of course defining BOOST_COROUTINES_NO_DEPRECATION_WARNING: <https://github.com/boostorg/beast/blob/010fb4b08c05ce82cf4a87d9985c5b4998d9…> But this warning happens when building the coroutine library not when compiling Beast's tests and examples. Regards

3 2

[release] 1.70.0 open for merging
by Marshall Clow 12 Dec '18

12 Dec '18

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

2 1

GSOC-19 Ideas
by Arihant Samar 12 Dec '18

12 Dec '18

Dear Boosters, I am new to the community. I wanted to ask if there will be any new suggested GSOC ideas for 2019. I went through the suggested proposals of 2018 but projects have already been done on most of them so It will be helpful if you could give some starting points. Sent from Mail for Windows 10 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 2

[release] Boost 1.69.0
by Marshall Clow 12 Dec '18

12 Dec '18

Release 1.69.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 numerous enhancements and bug fixes for existing libraries. For details, including download links, see < http://www.boost.org/users/news/version_1.69.0> You can also download directly from: < https://dl.bintray.com/boostorg/release/1.69.0/> SHA-256 sums: af05616f71006f97833e130aad886c96136457511ace4b5496d6566e69cbe0ca boost_1_69_0.7z 8f32d4617390d1c2d16f26a27ab60d97807b35440d45891fa340fc2648b04406 boost_1_69_0.tar.bz2 9a2c2819310839ea373f42d69e733c339b4e9a19deab6bfec448281554aa4dbb boost_1_69_0.tar.gz d074bcbcc0501c4917b965fc890e303ee70d8b01ff5712bae4a6c54f2b6b4e52 boost_1_69_0.zip 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, Daniel James, Micheal Caisse

2 3

[release] 1.69.0 closed for release
by Marshall Clow 12 Dec '18

12 Dec '18

The master branch is now closed for all changes except by permission. The commit-bot isn't running on master, so the super project will need to be manually updated for any changes. If all goes well, the release candidate should be out later today. Thanks, -- The Boost Release Team

4 7