April 2020 - Boost - lists.preview.boost.org

[release] Boost 1.72.0 Beta 1
by Marshall Clow 12 Apr '20

12 Apr '20

Boost release 1.73.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.73.0.beta.1/source/> The SHA256 checksums are as follows: 44f323b42c4375ab3751b67ac5ce53ba5267af20cf375be75675d8952d3cca4e ./boost_1_73_0_b1.7z 5270fa89243a3508331bd3773800de6d2f98d1f160b95e362fa8269d9cd58773 ./boost_1_73_0_b1.tar.bz2 82ffcd4a2e558a31f1ddd6a54ef6c00dae28b95c2ddee575c285544085dcb004 ./boost_1_73_0_b1.tar.gz 910b7560ee239472cc69e6a0c680dc4d9d7ea234faad807738ec98e4811c63d4 ./boost_1_73_0_b1.zip For details of what's in the release, see <https://www.boost.org/users/history/version_1_73_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

[release] Boost 1.73.0 Beta 1 Release Candidate 1
by Marshall Clow 10 Apr '20

10 Apr '20

The release candidates for the first 1.73.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.73.0.beta.1/source/ The release notes are not yet available. The SHA256 checksums are as follows: 44f323b42c4375ab3751b67ac5ce53ba5267af20cf375be75675d8952d3cca4e ./boost_1_73_0_b1_rc1.7z 5270fa89243a3508331bd3773800de6d2f98d1f160b95e362fa8269d9cd58773 ./boost_1_73_0_b1_rc1.tar.bz2 82ffcd4a2e558a31f1ddd6a54ef6c00dae28b95c2ddee575c285544085dcb004 ./boost_1_73_0_b1_rc1.tar.gz 910b7560ee239472cc69e6a0c680dc4d9d7ea234faad807738ec98e4811c63d4 ./boost_1_73_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

4 6

Re: [boost] [Boost-users] 404 GMane link in Boost.FileSystem doc
by Glen Fernandes 09 Apr '20

09 Apr '20

On Thu, Apr 9, 2020 at 6:15 AM Dominique Devienne wrote: > > Over at > https://www.boost.org/doc/libs/1_72_0/libs/filesystem/doc/reference.html#pa… > (and older version of the doc too) there's a link to > http://permalink.gmane.org/gmane.comp.lib.boost.devel/199744 > which is no longer so permanent :). According to https://en.wikipedia.org/wiki/Gmane > the website is no longer available. I guess any GMane link in docs should be updated > to another ML archive. Yes, the link should be updated to: https://lists.boost.org/Archives/boost/2010/02/162028.php Created https://github.com/boostorg/filesystem/commit/aaf54ada48b8da2bfc22b87d2890a… Glen

1 0

[release] 1.73.0 closed for Beta
by Marshall Clow 09 Apr '20

09 Apr '20

The master branch is now closed for all changes except by permission for the Beta release. Also, remember to add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_73_0.q… > Thanks, -- The Boost Release Team

1 0

1.73.0 Beta Deadline this Wednesday 4/8
by Marshall Clow 09 Apr '20

09 Apr '20

The deadline for major changes has passed. Upcoming dates: 8-Apr Boost 1.73.0 closed for beta ASAP Boost 1.73.0 beta 22-Apr Boost 1.73.0 closed for release ASAP Boost 1.73.0 release "ASAP", in this list, means "As soon as possible after the preceding milestone" -- Marshall

6 16

boost [math] excessive warnings via [lexical_cast] from [date_time] (and others) for clang 3.4?
by Jeff Garland 08 Apr '20

08 Apr '20

In the regression tables the following warnings are coming out of math config. I'm trying to understand what this means given that 1) the tests compile and execute fine, 2) the deadline is up, and 3) several of the cases are compiled in c++11 mode (is it pre conformance bc it's clang3.4?). I've seen this warning in other places that include lexical_cast as well. So sure I could go and define the macro to quiet this, but seems like that should be done closest to the source. In other words maybe math should only tell us that in headers that have a real issue? Or will this soon be a real issue? ../boost/math/tools/config.hpp:42:9: warning: CAUTION: One or more C++11 features were found to be unavailable [-W#pragma-messages] ../boost/math/tools/config.hpp:43:9: warning: CAUTION: Compiling Boost.Math in pre-C++11 conformance modes is now deprecated and will be removed from March 2021. [-W#pragma-messages] ../boost/math/tools/config.hpp:44:9: warning: CAUTION: Define BOOST_MATH_DISABLE_DEPRECATED_03_WARNING to suppress this message. [-W#pragma-messages] Full examples https://www.boost.org/development/tests/develop/developer/date_time.html https://www.boost.org/development/tests/develop/output/teeks99-dkr-dc3-4-98…

5 23

Gsod20 interest
by Damian Vicino 08 Apr '20

08 Apr '20

Hi, I'm wondering if there is interest in submitting boost as a potential org for Google season of docs (https://developers.google.com/season-of-docs) Also, if someone would like to be mentor on it, that would be great to know too. Best regards, Damian

2 1

Boost local unix domain example for IPC
by Jupiter 08 Apr '20

08 Apr '20

Hi, I am doing boost local unix domain for IPC, I midified the code based on sample code from boost_asio/example/local/stream_server.cpp, I am a little bit puzzled for errors calling different async_read, if I call original code using shared_from_this() it works fine: boost::asio::async_read(this->mSocket, boost::asio::buffer(this->mData), boost::bind(&session::HandleRead, shared_from_this(), boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred)); But if I tried to run a following lambda function which works in in my other boost asio TCP socket, it got an error "Operation canceled", what I could be missing here? Or do I have fundamontal problems in the lambda function I used for other TCP socket programs? boost::asio::async_read(this->mSocket, boost::asio::buffer(this->mData, sizeof(this->mData)), [=](const boost::system::error_code &status, const uint32_t size) {this->HandleRead(status, size);}); Thank you. Kind regards, - jh

2 2

[xpressive] Where are the names in the c_ctype.h file coming from
by Edward Diener 07 Apr '20

07 Apr '20

In the xpressive header file c_ctype.h there are names such as _ALPHA, _UPPER, _LOWER, _DIGIT etc. Where are these names declared or defined ? I searched through all the Boost libraries and did not find any of these names declared or defined anywhere. Are they supposed to be part of some C++ standard header file ?

1 0

Asio, gcc and -fconcepts
by Richard Hodges 07 Apr '20

07 Apr '20

Dear all, With the upcoming Boost 1.73 release imminent, I felt it was worthwhile pointing out that latest gcc has a problem with Asio if the `-fconcepts` command line flag is set. There is an issue in the Boost.Asio repo here relating to the manifestation of the bug in MSVC: https://github.com/boostorg/asio/issues/312 and an issue here in the Boost.Beast repo: https://github.com/boostorg/beast/issues/1884 It seems that the file boost/asio/detail/config.hpp was written when concepts support was not widespread and still in the concepts.ts stage. The syntax and capabilities of concepts were subtly changed during standardisation, with gcc and MSVC only supporting the C++20 dialect. Thus, compiling an Asio-based program with concepts enabled in either of gcc or MSVC fails unconditionally. I'm wondering if anyone has Chris' ear and might ask him to indulge us with a fix prior to the 1.73 release. I fear that by the time Boost 1.73 is in mainstream use, C++20 will be upon us we'll see an increase in issues and a loss of reputation as a result. Thanks for your time, Sincerely, -- Richard Hodges hodges.r(a)gmail.com office: +442032898513 home: +376841522 mobile: +376380212

3 4