- Boost - lists.preview.boost.org

boost::streambuf default size/capacity still set to 128 in spite of size provided in constructor.
by Aniket Pugaonkar 05 Dec '22

05 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 1500 for receiving a packet on socket). The initial allocation (buffer_.resize is done with 128. But when we call *buf.prepare(1500)*, 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. Regards Aniket. /// 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); } -- Thanks and regards, Aniket Pugaonkar

1 0

Reminder: Release notes
by Marshall Clow 29 Nov '22

29 Nov '22

If you’ve been meaning to write release notes for your library for the 1.81.0 release, now is the time to do it. ;-) — Marshall

2 1

[release] Boost 1.81.0 beta 1 released
by Marshall Clow 24 Nov '22

24 Nov '22

Boost release 1.81.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/ The SHA256 checksums are: 135f03965b50d05baae45f49e4b7f2f3c545ff956b4500342f8fb328b8207a90 boost_1_81_0_b1.tar.gz 736b041748d04c573d145613161cf2e54beb210c5511b67e6fac5510b82b6646 boost_1_81_0_b1.7z 941c568e7ac79aa448ac28c98a5ec391fd1317170953c487bcf977c6ee6061ce boost_1_81_0_b1.tar.bz2 c58d50acf58a98d4f5a7d891257d154efa50ca90312ca446586c7b4f9b7d3f14 boost_1_81_0_b1.zip Release notes (still need updates): https://www.boost.org/users/history/version_1_81_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- Boost Release Team

3 2

GSoC 2023
by David Bellot 21 Nov '22

21 Nov '22

Dear Boost developers, organization applications for the Google Summer of Code 2023 will start next year in January, that is in about 2 months from now. In order to prepare the application for Boost C++, I would like to have a list of interested mentors and the topics they would like to propose to their students. The Google Summer of Code is a good opportunity for Boost to try ideas or improve existing libraries. Contact me now if you have any questions and are interested in mentoring next summer. Cheers, David

4 4

minor incident report, boost.org
by Sam Darwin 16 Nov '22

16 Nov '22

Hi, This morning around 7am PST the boost.org website appeared to be unavailable. Upon investigation the cause of the problem was traced to DNS. boost.org resolved in DNS. However boost.org redirects to www.boost.org and that failed to resolve at the upstream DNS provider. # nslookup > server dns1.easydns.com > www.boost.org Server: dns1.easydns.com Address: 2400:cb00:2049:1::a29f:1835#53 ** server can't find www.boost.org: REFUSED A "dig" command also showed "..Request blocked by policy". After an hour or so, the situation cleared up. Most likely something at easydns.com. A similar event occurred earlier this year. The C++ Alliance has set up web proxies to alternative domains boostcpp.org and boostlibraries.org in case boost.org is unavailable. Those were online and may be used as a backup. Best Regards, Sam Darwin sam(a)cppalliance.org

1 0

Boost tarball release that works with CMake
by Mojca Miklavec 16 Nov '22

16 Nov '22

Dear developers, For a CMake-based project we need to fetch Boost sources as part of the build process (unless boost is already installed, in which case that version can be used). We are using CMake's FetchContent that recursively clones the repository from GitHub, but that process is extremely slow. On the Windows runner in GitHub actions it takes roughly 3 extra minutes to "git clone" boost alone (or 11 minutes for something like "choco install boost-msvc-14.3"). I tried to fetch the .7z file instead, but that one doesn't work because the CMake support gets stripped from the distributed sources when generating the tarballs. A single file would result in a much faster and more reliable workflow. The file can be cached on GitHub Actions, on a local computer one doesn't need to repeatedly clone the repository (which also slows down other parts of CMake) etc. I started the discussion here: https://github.com/boostorg/release-tools/pull/35 where it has been explained to me that: - either the CMake support needs to be heavily refactored (unlikely to happen soon) - or the project could generate one tarball using the layout that's consistent with git repository The second option might eventually be fulfilled automatically by GitHub, but that is probably not likely to happen any time soon either. I can imagine that creating one extra '.tar.xz' with a slightly different layout to support CMake builds might be straightforward to make. Is there any chance to fulfill my dream to be able to build a boost tarball with CMake out-of-the-box? Thank you very much, Mojca

7 10

The C++ Alliance
by Louis Tatta 15 Nov '22

15 Nov '22

Hello, my name is Louis Tatta and I am the CEO of The C++ Alliance, a non-profit founded by Vinnie Falco to support and bolster the C++ ecosystem through open source and education. This serves as a formal introduction and description of our recent activities to support Boost. As you all know, Travis CI (continuous integration) became unusable for Boost needs over a year ago. To ensure the availability of CI services, our CTO and chief of devops Samuel Darwin (“Sam”) has deployed Drone CI, an open source continuous integration framework, onto scalable Amazon Web Services instances rented by us. Over the last year there has been some turnover in terms of key individuals who administer the Boost website and support the Boost release process. We have made Sam’s time and expertise available to the Boost organization to support the release managers and core developers as needed to resolve IT issues. Vinnie has outlined a vision for revitalizing Boost by developing a new, modern website to stimulate technical discussion and publication of educational resources and ideas. To this end we have retained a design firm and the leading Python development house to build a new interactive website for Boost. The designs have been completed, and the coding for the website has been underway now for almost a year. Given the current trajectory we estimate that this project will be ready for internal viewing, testing, and feedback by authors and maintainers at the end of Q1 2023. Our current engineer staffing and projects are as follows: Klemens Morgenstern, a full-time Staff Engineer, is maintaining the Boost.Beast library and developing a new high client library built on Beast and Asio. Alan de Freitas, a full-time Staff Engineer, has been working on Boost.URL (now accepted) for the last year and has also taken over maintenance of Boost.StaticString. Dmitry Arkhipov, a part-time Staff Engineer is maintaining Boost.JSON, adding new features with guidance from Peter Dimov. Christian Mazakas, a full-time Staff Engineer and Joaquín M López Muñoz, a part-time Staff Engineer, have been working on the Boost.Unordered improvement project which is overseen by Peter Dimov. If anyone has questions about any of this please feel free to ask, or reach out to me by email.

1 0

[release] Boost 1.81.0 Beta 1 Release Candidate 2 is available
by Marshall Clow 15 Nov '22

15 Nov '22

Unfortunately, people found a few problems in the RC1 (Thanks to everyone who tried it, and especially to those who reported problems) We now have a RC2, available at: <https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/> The SHA256 checksums are as follows: bff5cf561ab65be658c030f6b348a4907cce039611e96112dc8f6e27b6a9f44b boost_1_81_0_b1_rc2.7z 7f300d48189b9f25bf3b214168912043681819f0ace332b0e9de503f7e23e72c boost_1_81_0_b1_rc2.tar.bz2 1619545e2f180caf6615eb83220ebcc1342c20704307b59871d987b95adb1326 boost_1_81_0_b1_rc2.tar.gz 3f9ebb8b23cab1617a7ae9a38b251e4803c917832b0c4c96b907cf122dec428f boost_1_81_0_b1_rc2.zip The changes are: 1) Fixed a compile error in Boost.ASIO 2) Fixed several compilation errors on Mac OS with libstdc++. (Boost.Config) 3) Fixed Boost.JSON compilation error with X11 4) Fixed a crashing but on shared_ptr on PPC (Boost.Sharedptr, Boost.Align) 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

2 2

[Release] Boost 1.81.0 closed for beta
by Marshall Clow 14 Nov '22

14 Nov '22

Master is closed for all changes. See the release schedule at: https://www.boost.org/development/index.html <https://www.boost.org/development/index.html> -- Release managers

3 3

[release] Boost 1.81.0 Beta 1 Release Candidate 1 is available
by Marshall Clow 13 Nov '22

13 Nov '22

Available at: <https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/> The SHA256 checksums are as follows: 6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z 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

8 10