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

[Test] How to make test framework create Core dump in case of any unhandled exceptions?
by Sergey P 21 Dec '22

21 Dec '22

Dear developers, Is it possible to force Boost.Test framework to create Core dump in case of catching any kind of unhandled exception from code that is being tested? We tried to use parameter: *--catch_system_error=no* but it creates core dump for system signals only, while we need core dump for any exceptions, even custom ones. We would appreciate any suggestions or hints. Thank you very much! Best regards, Sergey Podolyan

1 0

[release] Boost 1.81.0
by Marshall Clow 17 Dec '22

17 Dec '22

Release 1.81.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 one new library and numerous enhancements and bug fixes for existing libraries. * URL: A library for parsing, modifying, and printing URLs using only C++11, from Vinnie Falco and Alan de Freitas. For details, including download links, see <http://www.boost.org/users/news/version_1.81.0> You can also download directly from: <https://boostorg.jfrog.io/artifactory/main/release/1.81.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. -- The Boost Release Team Marshall Clow, Glen Fernandes, Michael Caisse

3 2

Master is open for merges
by Glen Fernandes 15 Dec '22

15 Dec '22

Master is open again, with no restrictions. Boost version numbers bumped (boost, config, more), and new release notes stubbed (website). Glen

1 0

[release] Boost 1.81.0 Release Candidate 1 is available
by Marshall Clow 14 Dec '22

14 Dec '22

The first release candidates for the 1.81.0 release are now available at: <https://boostorg.jfrog.io/artifactory/main/release/1.81.0/source/> The SHA256 checksums are as follows: 205666dea9f6a7cfed87c7a6dfbeb52a2c1b9de55712c9c1a87735d7181452b6 boost_1_81_0_rc1.tar.gz 6e689b266b27d4db57f648b1e5c905c8acd6716b46716a12f6fc73fc80af842e boost_1_81_0_rc1.zip d7bc4e2a2aee374a8c24832cacfed1265680c1e824d09fab3e00f87508155353 boost_1_81_0_rc1.7z 71feeed900fbccca04a3b4f2f84a7c217186f28a940ed8b7ed4725986baf99fa boost_1_81_0_rc1.tar.bz2 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 Release managers

10 15

Revitalization
by David Sankel 09 Dec '22

09 Dec '22

Hi all, At C++Now this year I gave a talk on the status of Boost and presented this graph which illustrated the trend of Boost mailing list participation. https://docs.google.com/presentation/d/1ocX8Dh4B98gxfXJTWOriaEU1tmJN61M4Rfj… I'm interested to hear your opinions as to what happened over that time period to cause such a trend. There's truth to the claim that this question is being asked of the wrong people; those who left, stopped participating, or would otherwise start probably have good insight. Nevertheless, I think it would be interesting for us to brainstorm on this. Thanks in advance for your thoughts. -- David

26 62

[ASIO] boos::asio::basic_streambuf does not accept user defined size during construction. Still defaults to 128
by Aniket Pugaonkar 09 Dec '22

09 Dec '22

Hello, I was checking the implementation of boost streambuf and noticed that buffer_delta value is defaulted to 128, which results in the capacity of the container to 128 bytes by default, and based on that, there is no way to change it even if we provide max size as some custom number (say 9000 for receiving an encapsulated packet on socket). The initial allocation (buffer_.resize is done with 128. But when we call *buf.prepare(9000)*, it again results in resize(n) operation (through reserve(n) function call. Is there any other way to change this other than modifying the constructor in our codebase to provide a user defined value of buffer_delta Not sure if this needs to be enhanced. the maximum_size argument seems to be of no use in this case. Kindly advise for the same. For time being, I modified the library code to the following to ensure it does not break the default argument, but accepts user defined value. Alternatively, I can change buffer delta to be of larger value, but don't want to end up with a large buffer for no reason. if (max_size_ == std::numeric_limits<std::size_t>::max()) pend = (std::min<std::size_t>)(max_size_, buffer_delta); else pend = std::max<std::size_t>(max_size_, buffer_delta); Regards Aniket. -------------------- original code ---------------- enum { buffer_delta = 128 }; /// Construct a basic_streambuf object. /** * Constructs a streambuf with the specified maximum size. The initial size * of the streambuf's input sequence is 0. */ explicit basic_streambuf( std::size_t maximum_size = (std::numeric_limits<std::size_t>::max)(), const Allocator& allocator = Allocator()) : max_size_(maximum_size), buffer_(allocator) { *std::size_t pend = (std::min<std::size_t>)(max_size_, buffer_delta);* *buffer_.resize((std::max<std::size_t>)(pend, 1));* setg(&buffer_[0], &buffer_[0], &buffer_[0]); setp(&buffer_[0], &buffer_[0] + pend); }

1 0

Biuld boost with MSVC
by Mauro Ziliani 09 Dec '22

09 Dec '22

Hi all. My name's Mauro. I need to build boost 1.80.0 against v141_xp MSVC toolset. Which is the correct syntax for bootstrap ot b2? Best regards, MZ -- https://www.linkedin.com/in/mauroziliani

1 0

[release] Master Branch is closed for all changes
by Marshall Clow 08 Dec '22

08 Dec '22

The master branch is closed for all changes. Release expected on 14-Dec-2022 - Release Managers

1 0

missing patch
by Gero Peterhoff 07 Dec '22

07 Dec '22

Hi Matt, i'm missing patch #871/#872 (https://github.com/boostorg/math/issues/871) in 1.81rc2. thx Gero

2 3

Master branch is now open for bug fixes
by Marshall Clow 07 Dec '22

07 Dec '22

The master branch is now open for bug fixes and documentation changes. Other changes by release manager permission, as described in https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy The next deadline: On December 7th, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/> — Marshall

12 27