March 2025 - Boost - lists.boost.org

Adding optional<T&> find like method to associative containers in boost.
by Ivan Matek 18 Jul '25

18 Jul '25

Hi everybody, I presume somebody thought of this before but for some reason it never happened, but just in case it was never discussed I wonder if people here believe adding an nicer version of find(with different name obviously) to associative containers in boost would be beneficial? Since boost::optional allows references this would work. I presume naming is what most people will have strong feeling about. I personally prefer ofind/oat since I love short names, Barry suggested different names in his blog <https://brevzin.github.io/c++/2023/05/23/map-api/>, e.g. try_at. boost::optional did not get all the updates C++23 std::optional got, e.g. transform that make this usage compose nicely, but those could be added to boost::optional.

13 85

[review] [sqlite]
by Richard Hodges 29 Jun '25

29 Jun '25

Dear All, Surprise! The Boost formal review of the Boost SQLITE library starts *TODAY*, taking place from November 13th, 2024 to November 22nd, 2024 (inclusive). I apologise profusely for springing this on you without prior warning. The error is entirely mine. I am extending the period by one day to compensate. The library is authored by Klemens Morgenstern (@klemens-morgenstern in the CppLang slack). Documentation: https://klemens.dev/sqlite/ <https://anarthal.github.io/mysql/index.html> Source: https://github.com/klemens-morgenstern/sqlite <https://github.com/anarthal/mysql/> >From the documentation: boost.sqlite is a simple to use C++ sqlite library. It provides a modern interface using facilities like error_code, views (e.g. for blobs) and the ability to use boost.describe or boost.pfr for parameterised queries. Supported features include: - typed queries - prepared statements - json support - custom functions (scalar, aggregate, windows) - event hooks - virtual tables SQLite provides an excellent C-API, so this library does not attempt to hide, but to augment it. Please provide in your review information you think is valuable to explain your choice to ACCEPT or REJECT including SQLITE as a Boost library. Please be explicit about your decision (ACCEPT or REJECT). Some other questions you might want to consider answering: - Will the library bring additional out-of-the-box utility to Boost? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - Will the choice of API abstraction model ease the development of software that must talk to a SQLITE database? - Are there any immediate improvements that could be made after acceptance, if acceptance should happen? - Did you try to use the library? With which compiler(s)? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? More information about the Boost Formal Review Process can be found at: http://www.boost.org/community/reviews.html The review is open to anyone who is prepared to put in the work of evaluating and reviewing the library. Prior experience in contributing to Boost reviews is not a requirement. Thank you for your efforts in the Boost community. They are very much appreciated. Richard Hodges - review manager of the proposed Boost.SQLITE library Klemens is often available on CppLang Slack and of course by email should you require any clarification not covered by the documentation, as am I.

19 67

Pretty printer module
by Дмитрий Архипов 14 Apr '25

14 Apr '25

Recently Niall Douglas posted about his idea to embed GDB pretty printers into binaries using a header. At the time I was thinking about a good way to deploy pretty printers for JSON that facilitates their autoloading. After Niall's post I experimented a little bit more, and I came to the conclusion that indeed nothing beats embedding via a C++ header in terms of convenience. At the same time I was also thinking about testing that pretty printers do in fact work. Given that pretty printers (usually) are implemented as a Python module, it initially looked like one could just run a Python program and import GDB Python modules. But actually you cannot. It turns out, though, you can run a Python script with GDB as the interpreter. After several iterations I arrived at this setup: https://github.com/boostorg/json/blob/develop/test/printers.cpp. A script converts this file into a Python script that uses GDB to break on certain lines and check if a particular expression produces a particular output when printed. While doing all this I thought that most of this work can be useful to other libraries. So, I moved the reusable parts into a separate directory (https://github.com/boostorg/json/tree/develop/pretty_printers) and added both a b2 module, and a CMake module. For B2. Importing: https://github.com/boostorg/json/blob/develop/build.jam#L8-L9 https://github.com/boostorg/json/blob/develop/build/Jamfile#L13 (Re)generating the header: https://github.com/boostorg/json/blob/develop/build/Jamfile#L88-L95 Testing: https://github.com/boostorg/json/blob/develop/test/Jamfile#L96-L101 For CMake: Importing: https://github.com/boostorg/json/blob/develop/CMakeLists.txt#L54-L55 (Re)generating the header: https://github.com/boostorg/json/blob/develop/CMakeLists.txt#L56-L63 Testing: https://github.com/boostorg/json/blob/develop/test/CMakeLists.txt#L80-L88 My questions to the community: do you find this useful? Would you use it in your Boost or non-Boost library? If you do, the module should be moved to tools rather than stay in libs/json.

12 26

boost::python and Python 3.12
by Tom Kacvinsky 13 Apr '25

13 Apr '25

While working on a project to upgrade an embedded Python interpreter (to Python 3.12), which uses boost::python, I noticed the structs from the Python C API now have more members and those extra struct members were not populated in the boost::python code. In particular I was bit by the enum module crashing our application startup. I noticed this with boost 1.78, but I found the same problematic code in the release that was current as of two months ago (1.87.0, I think). I got things to compile and run, but my approach was to just make the code Python 3.12 compliant. I can prepare a patch that has the appropriate macro guards for populating the structs as they relate to different Python versions. I'll read the boost developers guide and follow the necessary steps to submit a fix. Regards, Tom

2 2

[release] Master branch is now open for bug fixes
by Marshall Clow 02 Apr '25

02 Apr '25

Hi, The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in: https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy The next deadline: On April 2nd, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ — The release managers

6 12

Boost::MQTT5 and boost 1.82.0?
by Georg Gast 31 Mar '25

31 Mar '25

Hi Boost, i read here [1] that boost::mqtt5 needs boost 1.82.0 but it is published with 1.88.0 Beta1 How to use boost::mqtt5 with boost 1.82.0? > Boost.MQTT5 is a header-only library. To use Boost.MQTT5 it requires the following: > > C++17 capable compiler > Boost 1.82 or later. In addition to Asio, we use other header- >only libraries. > OpenSSL. If you require an SSL connection by using boost::asio::ssl::stream. [1] https://www.boost.org/doc/libs/1_88_0_beta1/libs/mqtt5/doc/html/mqtt5/intro…

2 2

Issue fixed in context library that is not included in 1.88 beta release?
by Anders Axelsson 29 Mar '25

29 Mar '25

Hi, I stumbled upon a problem found in the 1.87.0 release (and also 1.88 beta1) The issue seems to have been resolved on the develop branch in the actual submodule repo quite some time ago by another developer, but it is yet not included in the top/super project. The ticket: https://github.com/boostorg/context/issues/297 I am very new to the community, so I don't really know what is the typical way of working here. it would be sad if we miss to include an important build issue in the next release just because of some administrative issues, so I am happy to help but like I said, I am not familiar with how I can do that. Any ideas?

3 3

Asio Beta changes are missing on the 1.88 Beta page
by Dennis Luehring 27 Mar '25

27 Mar '25

Asio is missing on the beta release page https://www.boost.org/users/history/version_1_88_0.html but there seem to be changes available for the beta https://www.boost.org/doc/libs/1_88_0_beta1/doc/html/boost_asio/history.html

1 0

Reminder: Master branch closes for the 1.88.0 release NEXT WEDNESDAY
by Marshall Clow 26 Mar '25

26 Mar '25

Also, if you have release notes, now’s the time to write them. — Marshall

1 0

release] Boost 1.88.0 beta 1 released
by Marshall Clow 16 Mar '25

16 Mar '25

Boost release 1.88.0 beta 1 is now available at: https://archives.boost.io/beta/1.88.0.beta1/source/ The SHA256 checksums are: bc4948bc664fde0c2142badae2679a42124b464dc58019250afe0ef57fd7763e boost_1_88_0_rc1.zip 3c334a9a743b68a35452b0223be8932fb39f26a6938382f9b9e625c4df99602c boost_1_88_0_rc1.tar.gz 9e42c0611500151d795d66a07ef0a21036c02d24678e2e887caf6d97fcbc25ca boost_1_88_0_rc1.tar.bz2 7faf60c4cb12ee90270e41716cf3735a8739016d7346983ce9f5e899e510b26d boost_1_88_0_rc1.7z Release notes (still need updates): https://www.boost.org/users/history/version_1_88_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