July 2024 - Boost - lists.preview.boost.org

Two mqtt libraries
by Robert Ramey 03 Oct '24

03 Oct '24

I've been contacted by my friend and sometime collaborator Takatoshi Kondo regarding his submission of a boost library: https://github.com/redboltz/async_mqtt. It has received two endorsements. He has asked me to be review manager and I'm inclined to accept this request as he was very helpful to me during the refinement of the boost serialization library. There is also mqtt client library that is proposed to the Boost. https://github.com/mireo/async-mqtt5 It also has endorsements and a review manager. A cursory examination of the git hub pages suggest considerable overlap between the two submissions. In general, boost has discouraged the acceptance of multiple libraries with this much overlap - and for good reason. An accepted library often becomes the canonical implementation in large parts of the C++ world. Having two high quality libraries that do almost the same thing is not where we would like to be. I would like to propose that we review both libraries simultaneously in order to try to reach a consensus as to which, if either we want to accept. I know this is a difficult task, but I think it is important that we do this. It's going to be tough to reject a well written library because a better one has been accepted. But it would be worse to reject a well written library merely because another one was submitted first. Normally I don't participate as a review manager as I'm pretty bogged down in Boost stuff as it is. But I'm willing to make an exception in this case due to the importance of this case and my strong personal ties to Takatoshi. BTW - who is the review wizard these days? I presume that he will be the one making the decision about this. Robert Ramey

10 17

Re: [boost] [compute] Maintenance status
by René Eng 18 Aug '24

18 Aug '24

Hi all I am no expert in OpenCL nor GPGPU, but very interested in this topic and would love to learn more about it. I volunteer to take care of the maintenance of this library. Since I have no experience with the Boost way of handling PRs etc., I guess would need some support from an experienced library maintainer in the beginning. Until now I was a silent reader here, so let me shortly introduce myself: My name is René Eng, 57 years old, living in Switzerland. I am working as a C++ developer for more than 20 years, in the high performance/low latency area. I have experience with some other Boost sub-libraries, in the past also used b2 to build Boost when there were no packages available yet. If there is no-one else with more experience in this topic, who wants to take over this library, I would. This week I am on holiday, so I would actually start to take a closer look into it next week. Best regards René Von meinem iPhone gesendet > Am 21.07.2024 um 17:04 schrieb Joaquin M López Muñoz via Boost <boost(a)lists.boost.org>: > It was brought to my attention that Boost.Compute seems to be all but abandoned: > no updates in three years, more than 100 issues filed, 27 unattended PRs. This is a > shame given that the library looks pretty popular based on GH stars and references > on Internet. Are there volunteers to take on maintenance of the library? > > Best, > > Joaquin M Lopez Munoz > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 2

[Boost][BGL] new planar_vertex_coloring.hpp ?
by hermann＠stamm-wilbrandt.de 15 Aug '24

15 Aug '24

I have some experience in using BGL and porting my non-BGL graph code to BGL. I want to create pull request for generating random maximal planar graphs. I have 1994 technical report non-BGL implementation on gihub. So before porting that, I want to get some experience on the Boost pull request and review process. I made use of the many planar graph algorithms in straight_line_graphviz.cpp gist: https://gist.github.com/Hermann-SW/99d151a273d290ee0d843c79b2da26a8 So I thought on a providing planar graph vertex coloring algorthm(s) as handson. I would start by taking https://www.boost.org/doc/libs/1_85_0/libs/graph/doc/sequential_vertex_colo… as a template for "planar_vertex_coloring.hpp". My plan is to first port my existing fast linear time "six_coloring()" https://github.com/Hermann-SW/planar_graph_playground/blob/main/c%2B%2B/und… and learn about the review process with it. Later I would implement one of the several linear time "five_coloring()" algorithms: https://en.wikipedia.org/wiki/Five_color_theorem#Linear_time_five-coloring_… And probably the quadratic time "four_coloring()" algorithm mentioned there as well. I looked at commits in Boost graph directory and there is not that much recent activity. Is my plan and the steps outlined the right way to start? Regards, Hermann Stamm-Wilbrandt.

1 3

CMake Announcement from Boost Steering Committee
by Jon Kalb 13 Aug '24

13 Aug '24

The libraries produced by the Boost community have had a greater impact on the way that the C++ community writes code than any other library implementation. The focus of the Boost community will always be on the libraries, but it is undeniable that we are dependent on and often limited by the infrastructure of our trade. Years ago, the move to Git was contentious; yet, it was required to improve development. In a similar vein our build system has become an impediment for many developers and users, existing and prospective. Therefore, we, the Steering Committee, announce to the Boost community our desire and intent to move Boost’s build system to CMake for users and developers alike. We are soliciting comments and proposals from the community to guide the process and the goals. Our desire is that the community can come to consensus by the end of the calendar year with a vision of supporting users and developers. We understand that the actual process of achieving the end goal will be long, time consuming, and not without its share of conflict. We also recognize that the Boost community is comprised of bright and passionate individuals that are eager to get involved and help get work done. The members of the Steering Committee have been encouraged by the discussions and activity surrounding CMake on the mailing lists over the years and know that many people have voiced visions. We hope that each of you rejoins the discussion to support this initiative and contributes to the common goal of improving Boost’s integration into the broader C++ ecosystem. For the Boost Steering Committee, Jon Kalb, Chair jonkalb(a)boost.org

49 199

[config] First steps towards C++20 modules
by Antony Polukhin 12 Aug '24

12 Aug '24

Hi, C++20 modules seem to be a good tool to improve compile times and to hide the implementation details of the libraries. I've been looking throught the sources of {fmt} library. Looks like the fmt library approach to C++20 modularization seems to fit Boost quite well. How about adding the following macro to Boost: * BOOST_BEGIN_MODULE_EXPORT - starts the scope of things to export if Boost is build as a C++20 module * BOOST_END_MODULE_EXPORT - ends the scope of things to export if Boost is build as a C++20 module * BOOST_MODULE_EXPORT - for a single entity export if Boost is build as a C++20 module As a result, if Boost is build as a module the above macros are defined in the following way: #define BOOST_MODULE_EXPORT export #define BOOST_BEGIN_MODULE_EXPORT export { #define BOOST_END_MODULE_EXPORT } Helper macro BOOST_NO_CXX23_IMPORT_STD for detecting availability of `import std` also seems useful. Macro BOOST_NO_CXX20_MODULES - for notifying the libraries that compiler does not support modules or Boost modules are not compiled. With all the above macros the Boost libraries could look like: /// header #include <boost/library_that_is_known_to_not_support_modules.hpp> #ifdef BOOST_NO_CXX20_MODULES #include <boost/library_that_supports_modules.hpp> #else import Boost.LibraryThatSupportsModules; #endif #ifdef BOOST_NO_CXX23_IMPORT_STD #include <iostream> #else import std; #endif namespace boost { namespace detail { template <class T> bool try_do(const T&); } BOOST_BEGIN_MODULE_EXPORT template <class T, class From> bool try_lexiacal_convert(const From& f, T& to) { /*impl*/ } template <class T, class From> T lexiacal_cast(const From& f) { /*impl*/ } BOOST_END_MODULE_EXPORT } /// module src file export module Boost.MyLibraryName; #ifdef BOOST_NO_CXX20_MODULES #error ??? #endif #include <boost/my_library.hpp> -- Best regards, Antony Polukhin

5 14

Boost Governance?
by René Ferdinand Rivera Morell 09 Aug '24

09 Aug '24

A disclaimer: I write this solely as a Boost Library author. And not in any other capacity or representing any other interest. It's now been at least a year since Boost switched from the Software Freedom Conservancy to the Boost Foundation for its governance organization. But have people noticed any difference? Did you know that switch happened? Did you know that they held an election for the Board of Directors and for the Officers? Do you know when that election happened? Do you know who got elected? Do you know how they were selected? Do you know what their responsibilities are? Do you know what their bylaws are? Do you know their financials? More importantly: Did you answer "no" to any of those questions? As a library author, I can say I definitely answered no to many of those questions. This is a problem. As authors, without asking, we should know those answers from the organization that governs our work. We should have input into how that organization governs. In other words, we deserve open and transparent governance; not the closed and opaque status quo. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

10 9

New Logo Discussion
by Vinnie Falco 09 Aug '24

09 Aug '24

Hi. It is CppCon 2024 season, and the C++ Alliance is working on letting people know all the new and exciting things happening in Boost. We're doing this with Boost labeled conference shirts, and a beautiful brochure. You can see a draft of this promotional piece here (note: work in progress): https://cppalliance.org/pdf/Boost-Brochure-CppCon-2024.pdf The new Boost logo was developed by the Alliance, and a community consensus is needed if we are to fully move forward with its use. I am hoping this will spark the necessary discussion. Here are things to consider: * The logo is professionally designed by https://grainandmortar.com/ at a cost of $12,000 * Peter Dimov likes the image (this should not be construed as his endorsement or opposition to any of the above). * The image is a trademark of The C++ Alliance: https://tsdr.uspto.gov/#caseNumber=98417319&caseSearchType=US_APPLICATION&c… * Usage of the logo is governed by our Logo Usage Policy, a product of legal review at a cost of $4,000: https://www.boost.io/doc/contributor-guide/docs/logo-policy-media-guide.html * The Logo Usage Policy allows free usage without permission in Boost-related contexts. Otherwise, explicit written permission from the Alliance is required. * Trademark ownership by a registered entity with sufficient resources is necessary to protect the mark, which David Sankel alludes to here: https://lists.boost.org/Archives/boost//2024/03/256092.php * Adopting this logo costs Boost nothing. If our proposed arrangement stops working for the community, the libraries can easily adopt a different logo (including the old one, or none). Put simply, I am asking the Boost community to entrust The C++ Alliance.with the responsibility of establishing and maintaining this new Boost logo. Thanks :)

18 63

Paul Bristow
by John Maddock 08 Aug '24

08 Aug '24

I've just heard that Paul Bristow who helped so much with the development of Boost.Math and indeed many other libraries, passed away peacefully last week. RIP Paul. Much missed. John.

6 5

[outcome] Inline GDB pretty printing support
by Niall Douglas 08 Aug '24

08 Aug '24

Dear Boost, The biggest new feature to land into Outcome since it went ABI stable is inline GDB pretty printing support, whereby we embed into all binaries using Outcome the Python script to display the state of `result<>/outcome<>`. As Outcome uses a layered inheritance technique to match triviality of member functions from its configured types, having to click down through the layers to discover the state was always frustrating. MSVC has long shipped with a visualiser to eliminate this, so now support for GDB matches MSVC support. The relevant implementation file can be found at: https://github.com/boostorg/outcome/blob/master/include/boost/outcome/outco… I would appreciate any testing and reporting of any issues or bugs before the 1.86 bugfix window closes. It should "just work" once you have enabled inline script loading in your `.gdbinit`. Thanks, Niall

10 19

A Follow Up to My Original Note Re The Future of Boost
by Kristen Shaker 06 Aug '24

06 Aug '24

Hello Everyone, Thank you for patiently waiting while we had the opportunity to discuss things. Many of you have not heard my name before - this is largely because as a board, we do much of the non - dev work behind the scenes, such as administrative tasks like paying bills. However, I do want to take this opportunity to introduce myself quickly and to emphasize that - should anyone wish to reach out to me directly - I am happy to correspond via phone or email. My name is Kristen - I spent many years at Google on the C++ Core Libraries Team. I am heavily involved as an organizer in CppCon and C++Now. If anyone is curious about what I did at Google, I did give a talk <https://www.youtube.com/watch?v=torqlZnu9Ag> on automated refactoring and Clang Tidies that you can find on Youtube. My duties as Board Chair involve sending out meeting agendas, taking meeting notes, and collating meeting minutes. It is not our role to lead, but rather to support the Boost project. The leadership and direction of the Boost project has and should remain with the Boost Developers. The original Boost Steering Committee home page articulates its purpose as follows: “In the Boost community decisions have always been made by consensus and individual members have shown leadership by stepping forward to do what they felt needed to be done. Boost has not suffered from a lack of leadership or volunteer participation. It is not the role of the Steering Committee to inhibit this kind of spontaneous leadership and action, which has served Boost and the wider C++ community so well. On the contrary, it is the role of the Steering Committee to facilitate community-based leadership and decision making. The role of the Committee is to be able to commit the organization to specific action either where funds are required or where consensus cannot be reached, but a decision must be made.” We generally encourage any Boost Developer who would like to be more involved in administrated or organizational decisions to consider joining the board. We have multiple open board seats. Several Boost Developers are on the board and additional developers have been invited in the past - however they have decided against joining due to their distaste for the type of administrative work we do. We would love to hear more from you. Please reach out. You can reach all of us at once via boostfoundationdirectors(a)boost.org. Additionally, if you’d like to attend one of our board meetings, we regularly host guests. The C++ Alliance and the Boost Board of Directors have had their disagreements. Recently, it has become apparent - in particular via their attempt to purchase the boost.org domain name and the proposed new Boost Logo - that The Alliance would like to exert a greater sense of ownership over Boost Library assets. The desired control over assets is what I was referring to in my original note regarding their attempt to take ownership over the Libraries. While the C++ Alliance is a non profit organization, it is wholly funded and effectively controlled by one individual - Mr. Falco. The Board of Directors has a stewardship responsibility to Boost and we are wary of a single individual exerting such a level of control over the Boost Libraries. The Board has existed for many years and will continue to exist - as new members are regularly on boarded as tenured ones retire. Given the structure of the Board and the nature of the volunteer work, we believe ourselves to be the more permanent entity. Many have mentioned a desire for cool headed coordination between the two organizations. I also believed this to be the most advantageous outcome, so I reached out to Mr. Falco to establish a direct line of communication. Even now I would characterize our personal relationship as quite positive. Due to some pre-existing personality clashes, it is now our understanding that Mr. Falco believes collaboration to be an impossibility. Therefore, a large part of Mr. Falco’s motivation to acquire the domain name stemmed from a desire to cut the Board of Directors out of all future decision making processes. Given that I believed we had made great progress toward greater collaboration, I was personally gutted by this turn of events. Accordingly, we did not see a well lit path forward regarding coordination between the Boost Board and the C++ Alliance. This decision was in no way meant to minimize the great contributions The Alliance has made to the Boost Libraries. We do not want to discourage Alliance members from contributing to Boost. This is fundamentally a question about the stewardship of the Boost Library Assets. As mentioned above, the Boost Board of Directors exists largely to facilitate community based decision making. Accordingly, we feel the most appropriate thing to do at this juncture would be to let the developers make a decision on how they would like to proceed regarding what level of ownership the C++ Alliance should have on Boost Library assets. Here are what we believe to be the available options. 1. The C++ Alliance assumes control of the Boost assets, including the boost.org domain name. The Boost Foundation becomes uninvolved in any decisions related to the Boost Libraries. 2. The Boost Foundation continues to be the stewards of the boost.org domain name and related assets. New assets that are meant to be associated with the Boost Libraries are transferred to the Boost Foundation. In any matters related to the Boost Libraries, the Board will abide by any decisions made by the developers but will no longer vote themselves on issues as they relate to the Boost Libraries unless there truly is no clear consensus or path forward. There was some discussion about the assets being held in a third party non profit controlled by a subset of the Boost Developers. However, given that there are already many Boost Developers on the Boost Foundation Board of Directors, we don’t see this as a meaningful deviation from the status quo. Also as one final note, many on the mailing list expressed a distaste for the political nature of this disagreement. Of course, being involved in political spats is not why you joined Boost! We completely understand this. Believe me when I say we don’t like dealing with political disagreements either - no one does. They’re draining and they can distract from an organization’s larger mission. However, sometimes, they are truly unavoidable. We’re articulating our thought process here, not to annoy you, but so every Boost Developer has a say in how things turn out. Warm Regards, The Boost Board of Directors Also here are some answers to some of the more specific questions. There were a lot of them and I believe some were answered in the preceding paragraph. Sincerest apologies if I missed a question or two. Beman Dawes did pass away in 2020. The Boost Foundation did take action when the domain expired. In fact, Michael Caisse spent many hours on the phone with support figuring out how to pay for the bill so the website would be accessible. Additionally, he invested significant time in procuring the death certificate so we could own the domain. Progress was being made, albeit slowly.

21 41

Notice of Intent To Redirect boost.org to boost.io
by Vinnie Falco 02 Aug '24

02 Aug '24

All: A consensus to launch the new Boost website was reached by both the community and the Boost Foundation. Since then, the Foundation has: * Ignored the consensus decision reached in April [1] * Prevented the C++ Alliance's attempt to secure the boost.org domain [2] * Launched the competing "Beman Project" [3] * Voted to "cut ties with the Alliance" [4] * Avoided important questions asked on the mailing list, for over a month As it is clear now that Foundation control of the boost.org domain may be harmful to Boost, the existing website will be redirected to the new website. Absent objection, this pull request to redirect boost.org to boost.io will be merged on August 5, 2024: https://github.com/boostorg/website/pull/861 Thanks [1] https://lists.boost.org/Archives/boost/2024/04/256602.php [2] https://cppalliance.org/pdf/Domain-Name-Purchase-Agreement.pdf [3] https://www.bemanproject.org/ [4] https://cppalliance.org/pdf/Boost-Foundation-Minutes.pdf

6 11

Master branch is now open for bug fixes
by Marshall Clow 31 Jul '24

31 Jul '24

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 Release manager permission is not needed for test changes or documentation changes. The next deadline: On August 7th, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ — Marshall

7 11

Requesting permission for a trivial change to LEAF
by Emil Dotchevski 29 Jul '24

29 Jul '24

It would be nice to include in the current release this small change that marks leaf::result objects as nodiscard: https://github.com/boostorg/leaf/commit/1f745805553934cd76a241649cd9bafa277… . Thanks, Emil

1 0

[release] Boost 1.86.0 beta 1 released
by Marshall Clow 26 Jul '24

26 Jul '24

Boost release 1.86.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.86.0.beta1/source/ The SHA256 checksums are: 6c3b6b6b1760090ebd658b764c9006d9579df2a20763ede356e059fe52989277 boost_1_86_0_b1.tar.bz2 cc0e5c0fb54ea8762c2eb9fbfd185cb8ccbe1ad33c218883f9438dbe2f9a795b boost_1_86_0_b1.zip cad677f5b746bd83c68131766554b56ebf40eb7ba94823526b03820db9dbc049 boost_1_86_0_b1.7z 82b59c0ca4d3b8bbf910ffdbbf535ef738fa1d648b8ba6f2608b516a58f89c55 boost_1_86_0_b1.tar.gz Release notes (still need updates): https://www.boost.org/users/history/version_1_86_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. Thanks especially to Sam Darwin for his help with the tools, and figuring out what happend with RC3. -- Boost Release Team

1 0

Re: [boost] [release] Boost 1.86.0 Beta 1 Release Candidate 4 is available
by tobi＠die-loews.de 26 Jul '24

26 Jul '24

1 0

[release] Boost 1.86.0 Beta 1 Release Candidate 4 is available
by Marshall Clow 25 Jul '24

25 Jul '24

[ RC3 was malformed as a result of some tooling failures ] The fourth (and hopefully final) RC for the 1.86.0 Beta release is now available. Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: cad677f5b746bd83c68131766554b56ebf40eb7ba94823526b03820db9dbc049 boost_1_86_0_b1_rc4.7z 6c3b6b6b1760090ebd658b764c9006d9579df2a20763ede356e059fe52989277 boost_1_86_0_b1_rc4.tar.bz2 cc0e5c0fb54ea8762c2eb9fbfd185cb8ccbe1ad33c218883f9438dbe2f9a795b boost_1_86_0_b1_rc4.zip 82b59c0ca4d3b8bbf910ffdbbf535ef738fa1d648b8ba6f2608b516a58f89c55 boost_1_86_0_b1_rc4.tar.gz Changed libraries between RC2 and RC4: Boost.Process fixed some build issues on Windows 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

5 7

Boost 1.86 release notes?
by Andrzej Krzemienski 25 Jul '24

25 Jul '24

Hi Everyone, Are 1.86 beta release notes available anywhere? I recall that the beta release documentation used to be put on boost.org. Regards, &rzej;

2 1

[release] Boost 1.86.0 Beta 1 Release Candidate 3 is available
by Marshall Clow 24 Jul '24

24 Jul '24

The third (and hopefully final) RC for the 1.86.0 Beta release is now available. Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: a632d1e1465804b26f4d73112f1142c89caf74b026395df2e63a8c8972ac3ab0 boost_1_86_0_b1_rc3.tar.gz e061d83644568178ddece4bd3e241fb2656f49d6157c5d9fbff6c2fa74b1e328 boost_1_86_0_b1_rc3.zip e7f07bbc14915469b1ef80337c16e7a592f3eb547ba2cca828253c0a32372399 boost_1_86_0_b1_rc3.tar.bz2 91dcd8f980362c1c32bf8cc547c547fb02619bea877738b478c052926edc6a2d boost_1_86_0_b1_rc3.7z Changed libraries between RC2 and RC3: Boost.Process fixed some build issues on Windows 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

1 1

[release] Boost 1.86.0 Beta 1 Release Candidate 2 is available
by Marshall Clow 24 Jul '24

24 Jul '24

Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: c62c9ab3c448ef4ed1b45f69631e3d7cc425fca96b991e5007b3af49f84344e1 boost_1_86_0_b1_rc2.zip 7e5b42428ed30a7ac9d832e9df9f5150a29d9cffe5aebde4d4c109da89f54b77 boost_1_86_0_b1_rc2.tar.gz 8718b092b37f04a739b647d154901d923fb3c3cdcff9f793d6a472e3f8e7c647 boost_1_86_0_b1_rc2.7z cd63cd3110fafbed8c196a82dd0f72c8600bc5c7fc218ede213947da3b721c06 boost_1_86_0_b1_rc2.tar.bz2 Changed libraries between RC1 and RC2: Boost.Process Boost.Odeint 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

3 3

[release] Status of the Beta release
by Marshall Clow 24 Jul '24

24 Jul '24

We’ve had some problems with the RCs for the 1.86.0 beta. The RC1 had problems with Boost.Odient and Boost.Process. We had an RC2 yesterday, but that didn’t fix all of the Boost.Process build problems. There will be an RC3 today, which (hopefully) will fix them . If nothing else is found the beta release will be Friday. — Marshall

1 0

[release[ Boost 1.86.0 Beta 1 Release Candidate is available
by Marshall Clow 23 Jul '24

23 Jul '24

Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: 90be7ebbaf1c81a849791eb0f49d05a9ec7dbd0ec98b974dfe31d44d811e8298 boost_1_86_0_b1_rc1.7z 543ca3b743250a8b24b25c71209cf911c35613910e78a320835c21c053212ef2 boost_1_86_0_b1_rc1.tar.gz 1bf831ed717fa3e01db6c1f104b95f5a6a8d098a4cc9e61fa6eb81969c78645f boost_1_86_0_b1_rc1.tar.bz2 f739f8761bee6006c60a39fd21ed80b7b0a681c9ed448d1ae1bb28d8d8a69659 boost_1_86_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 Release Managers

7 13

[Release] Master branch is closed for beta
by Marshall Clow 23 Jul '24

23 Jul '24

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

3 4

Q2 2024 Transparency Report on Boost C++ Library
by Louis Tatta 22 Jul '24

22 Jul '24

Hello, Louis Tatta here, CEO of The C++ Alliance, Inc, a registered 501(c)(3) non-profit organization dedicated to supporting C++. This is our Q2 2024 transparency report on our charitable work for the Boost C++ Library Collection. The C++ Alliance actively seeks out highly talented and experienced C++ experts, hiring them, often full-time, so they can fully dedicate themselves to open-source projects. Our Staff Engineers maintain existing Boost libraries, develop new ones, and contribute to other Boost projects. We also employ IT experts full-time to maintain and enhance the infrastructure supporting Boost. This includes the legacy web server, the Drone continuous integration servers, deployment scripts for GitHub Actions on Boost repositories, and scripts that publish Boost releases. Additionally, we provide on-demand technical support services for Boost authors and maintainers facing infrastructure-related issues. The Boost Mailing List remains the premier venue for high-quality discussions on Boost libraries and related C++ Standards topics. The C++ Alliance continues to support the mailing lists, upgrading them to the latest Mailman version and developing an optional web-based front-end for browser-based interaction. We also manage the Official C++ Language Slack Workspace ( https://cpp.al/slack) hosting the most popular interactive discussions on Boost libraries. The C++ Alliance sponsors a paid plan to offer full history, video and audio conferencing, collaboration tools, and unlimited document storage for seventeen dedicated Boost library channels and one main Boost discussion channel. Our largest project for Q2 2024 is the ongoing development of the new Boost website. This new site will be a C++ social media portal with rich support for user-generated content and a robust back-end that provides visibility into contributions made on GitHub and the release process. Our goal is to deliver an enhanced user experience that attracts fresh talent to Boost. Notably, the website features hand-drawn graphics by our contract artist, reflecting our commitment to ensuring Boost not only functions well but also looks visually appealing. In Q2 2024 there were a total of zero Boost Formal Reviews. There were two petitions for endorsement for potential Boost candidates: *async_mqtt from Takatoshi Kondo (https://github.com/redboltz/async_mqtt) *multi from Alfredo Correa (https://gitlab.com/correaa/boost-multi) There's another MQTT library in the works proposed on Nov 2023, Async.MQTT5 from Ivica Siladic, Bruno Iljazovic and Korina Simicevic ( https://github.com/mireo/async-mqtt5) There were a total of three messages from the @Boost_Libraries X (formerly Twitter) account, all submitted by C++ Alliance team members. One of them featured artwork from Bob Ostrom, commissioned by us. Posts with visuals are three times more engaging than those with just text. We see the X platform as a vital tool for educating newer generations about the benefits of Boost. A total of $526,000 was spent on Boost-related contributions, broken down thusly (and rounded to the nearest thousand): Staff Engineers Compensation $392,000 Website Software Development $111,000 Server Hosting $23,000 During Q2 2024 we employed a total of 13 individuals to contribute to Boost. Here is a high-level summary of accomplishments: Sam Darwin (Chief Technical Officer) - Summary: Sam Darwin led major projects, overseeing the integration of new features in the Boost infrastructure. He coordinated between teams, ensuring smooth transitions and high-quality deliverables. His leadership was pivotal in the development of the new Boost website and improvements to the mailing list system. - Link: Sam Darwin's Q2 Update <https://cppalliance.org/sam/2024/07/10/SamsQ2Update.html> Dmitry Arkhipov (Staff Engineer) - Summary: Dmitry Arkhipov focused on maintaining and enhancing Boost libraries. He implemented several bug fixes, optimized existing code, and contributed to the development of new libraries. Dmitry also played a significant role in the continuous integration and deployment processes. - Link: Dmitry Arkhipov's Q2 Update <https://cppalliance.org/dmitry/2024/07/12/dmitrys-q2-update.html> Alan de Freitas (Staff Engineer) - Summary: Alan de Freitas worked extensively on the Boost website redesign, particularly on the back-end systems that support user-generated content and GitHub integration. He also contributed to developing new libraries and maintaining existing ones. - Link: Alan de Freitas's Q2 Update <https://cppalliance.org/alan/2024/07/13/AlanQ2Update.html> Christian Mazakas (Staff Engineer) - Summary: Christian Mazakas worked on enhancing Boost’s infrastructure, including optimizing server performance and improving deployment scripts. His contributions were crucial for maintaining the stability and efficiency of the Boost libraries. - Link: Not provided. Krystian Stasiowski (Staff Engineer) - Summary: Krystian Stasiowski focused on developing new features for existing Boost libraries and worked on performance optimizations. His work included contributing to the ongoing development of new libraries and providing technical support to other Boost authors. - Link: Krystian Stasiowski's Q2 Update <https://cppalliance.org/krystian/2024/07/15/KrystiansQ2Update.html> Peter Turcan (Senior Technical Writer) - Summary: Peter Turcan was responsible for creating and updating documentation for Boost libraries. He ensured that all new features and libraries were well-documented, making it easier for users to understand and utilize Boost’s capabilities. - Link: Peter Turcan's Q2 Update <https://cppalliance.org/peter/2024/07/07/PeterTurcan-Q2-2024.html> Matt Borland (Staff Engineer) - Summary: Matt Borland contributed to the development of new libraries and enhancements to existing ones. His focus was on improving library performance and ensuring that the codebase remained robust and reliable. - Link: Matt Borland's Q2 Update <https://cppalliance.org/matt/2024/07/08/Matts2024Q2Update.html> Ruben Perez (Staff Engineer) - Summary: Ruben Perez worked on several infrastructure projects, including server maintenance and optimization. He also contributed to the development and maintenance of Boost libraries, focusing on performance improvements and bug fixes. - Link: Ruben Perez's Q2 Update <https://cppalliance.org/q2_update/2024/07/09/RubenQ2.html> Mohammad Nejati (Staff Engineer) - Summary: Mohammad Nejati was involved in developing new libraries and improving existing ones. He focused on optimizing code and ensuring that Boost libraries were efficient and reliable. His work also included providing technical support to other developers. - Link: Mohammad Nejati's Q2 Update <https://cppalliance.org/mohammad/2024/07/10/MohammadsQ2Update.html> Fernando Pelliccioni (Staff Engineer) - Summary: Fernando Pelliccioni contributed to the ongoing development of the Boost libraries, focusing on implementing new features and optimizing performance. His work was instrumental in ensuring the high quality and reliability of Boost libraries. - Link: Fernando Pelliccioni's Q2 Update <https://cppalliance.org/fernando/2024/07/08/FernandoQ2Update.html> Joaquin M Lopez Munoz (Staff Engineer) - Summary: Joaquin M Lopez Munoz worked on several key projects, including the development of new Boost libraries and enhancements to existing ones. His contributions focused on improving code efficiency and performance. - Link: Joaquin M Lopez Munoz's Q2 Update <https://cppalliance.org/joaquin/2024/07/06/Joaquins2024Q2Update.html> Kenneth Reitz (Staff Engineer) - Summary: Kenneth Reitz focused on developing and maintaining Boost libraries, implementing new features, and optimizing existing code. His work also involved providing technical support and contributing to the Boost website redesign. - Link: Kenneth Reitz's Q2 Update <https://cppalliance.org/kenneth/2024/07/12/KennethQ2Update.html> Braden Ganetsky (Junior Staff Engineer) - Summary: Braden Ganetsky, as a junior engineer, contributed to various Boost library projects. His work included implementing new features, fixing bugs, and assisting with infrastructure maintenance. Braden’s contributions were valuable in supporting the overall development efforts. - Link: Braden Ganetsky's Q2 Update <https://cppalliance.org/braden/2024/07/14/BradenQ2Update.html>

6 8

Modular Boost status..
by René Ferdinand Rivera Morell 21 Jul '24

21 Jul '24

Yesterday I created PRs for each library that introduces the changes to build (and some code) to implement the modular B2 building. I track all the PRs here: <https://github.com/users/grafikrobot/projects/1/views/2> All the library PRs are in Draft status, as we wait for the tool related PRs to get merged. You can read an explanation of the changes here <https://github.com/grafikrobot/boost-b2-modular/blob/b2-modular/README.adoc> (the explanations may differ slightly from current reality). IMPORTANT: The PRs are all "Draft" as I continue to monitor build errors from any CI errors in the PRs. And to address feedback from authors. After the current release the process will go something like this: * I fix any current fallout in draft PRs. * The 1.86 release happens. * The owners merge the tool PRs to develop and master. * I fix any fallout from that. * Authors, and owners, merge library PRs to develop and master. * I fix any fallout from that. * I create subsequent PRs for the global B2 Boost build infrastructure to remove the old non-modular dead code. * The 1.87 release happens. Questions? -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

1 0

[compute] Maintenance status
by Joaquin M López Muñoz 21 Jul '24

21 Jul '24

It was brought to my attention that Boost.Compute seems to be all but abandoned: no updates in three years, more than 100 issues filed, 27 unattended PRs. This is a shame given that the library looks pretty popular based on GH stars and references on Internet. Are there volunteers to take on maintenance of the library? Best, Joaquin M Lopez Munoz

1 0

Should include of quadmath.h in multiprecision/cpp_bin_float.hpp be guarded with ifdef BOOST_MATH_HAS_QUADMATH_H?
by Martin Jambor 19 Jul '24

19 Jul '24

Hello, because of a bug[1] in GCC 13 and earlier versions, the #include of quadmath.h in multiprecision/cpp_bin_float.hpp did not fail even when the header file was not present on the system and compilation succeeded as long as nothing from the header file was actually needed. The bug has been fixed in GCC 14 which all of a sudden leads to new build requirements and failures such as [2]. Examining this build failure, I noticed that in math/special_functions/fpclassify.hpp (which is indirectly included from multiprecision/cpp_bin_float.hpp) the existence of the header file is specifically tested and macro BOOST_MATH_HAS_QUADMATH_H is defined or not accordingly. So I wanted to ask the question in the $subject. Could, or perhaps even should the include (together with its uses introduced in commit 4911125248bd) be guarded also by BOOST_MATH_HAS_QUADMATH_H and not just by BOOST_HAS_FLOAT128? Thank you, Martin [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753 [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1225861#c7

2 1

Boost Foundation, Boost, and the Beman Project
by Peter Dimov 19 Jul '24

19 Jul '24

Hi all, I recently brought up (by e-mail) the subject of the relationship between the Boost Foundation and the Beman Project before the BF board. I expressed the opinion that, since the Boost Foundation's primary purpose is to support Boost, the Beman Project should eventually have its own backing entity (foundation/nonprofit), instead of the existing Boost Foundation supporting both. David Sankel responded, quoted Boost Foundation's mission statement: "The Boost Foundation’s broad C++ mission is: (a) development of high quality, expert reviewed, legally unencumbered, open-source libraries, (b) inspiring standard enhancements, and (c) advancing and disseminating software development best practices. It does this by fostering community engagement, nurturing leaders, providing necessary financial/legal support, and making directional decisions in the event of Boost community deadlock." and helpfully pointed out that it very much doesn't say that supporting Boost is the primary purpose of the Foundation. And indeed, if one pays attention to the above, one would notice that Boost only appears once, at the end, somewhat incidentally, and as an afterthought. Unsurprisingly, I disagree. I think that the primary purpose of an entity named "the Boost Foundation" should be to support Boost, and if it currently isn't, something not quite right. At the moment I'm not proposing anything yet; this is purely informative. But no matter how I look at it, I see a pretty fundamental difference of opinion, which we'll need to deal with at some point.

12 32

Re: [boost] Boost Digest, Vol 7285, Issue 2
by Adam Getchell 19 Jul '24

19 Jul '24

> Date: Wed, 17 Jul 2024 13:38:58 -0700 > From: Vinnie Falco <vinnie.falco(a)gmail.com> > To: boost(a)lists.boost.org > Cc: Robert Ramey <ramey(a)rrsd.com> > Subject: Re: [boost] New Logo Discussion > Message-ID: > <CA+EzHGfmxMdhD04BCYz4Rvzk663KejBa+8QDF1fX84ZW1A3Ytg(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Wed, Jul 17, 2024 at 12:42?PM Robert Ramey via Boost < > boost(a)lists.boost.org> wrote: > >> FWIW - I much prefer the current logo which was developed by community >> inclusive process with many submissions and designs. >> > > Thanks. Upon reviewing my initial post I think I could have communicated > more clearly. Will everyone please vote on one of the following two options: > > 1. Boost adopts the proposed new logo with Alliance as custodian of the > trademark > > 2. No change I’m not sure I’m a voting member, but I like the new logo. Thanks also for doing all the legal review stuff. -- Adam Getchell https://adamgetchell.org <https://adamgetchell.org/>

2 1

Re: [boost] New Logo Discussion
by Joel de Guzman 18 Jul '24

18 Jul '24

On 7/18/24 9:36 AM, René Ferdinand Rivera Morell wrote: > On Wed, Jul 17, 2024 at 6:50 PM Joel de Guzman via Boost > <boost(a)lists.boost.org> wrote: >> On 7/18/24 3:49 AM, René Ferdinand Rivera Morell via Boost wrote: >>> On Wed, Jul 17, 2024 at 2:42 PM Robert Ramey via Boost >>> <boost(a)lists.boost.org> wrote: >>>> On 7/17/24 11:59 AM, Vinnie Falco via Boost wrote: >>>>> Hi. It is CppCon 2024 season, and the C++ Alliance is working on letting >>>>> people know all the new and exciting things happening in Boost. We're doing >>>>> this with Boost labeled conference shirts, and a beautiful brochure. You >>>>> can see a draft of this promotional piece here (note: work in progress): >>>>> >>>>> https://cppalliance.org/pdf/Boost-Brochure-CppCon-2024.pdf >>>>> >>>> FWIW - I much prefer the current logo which was developed by community >>>> inclusive process with many submissions and designs. >>> It wasn't. The logo picked by the community in that process was never >>> used. What is currently used was the result of private design between >>> the Boost Steering Committee and the artist that "won" that logo >>> contest. >> That is not correct. I was one of the major proponents of that logo contest (if not >> spearheded it). >> And I am not a member of the Boost Steering Committee. That contest was public and was >> discussed in the Boost list. It is NOT a private design. >> >> Here's part of the discussion (I do not have time to search all): >> https://lists.boost.org/Archives/boost//2005/03/81416.php >> >> You can see clearly I was asking for votes. > I did not claim the logo contest was not community driven and resulted > in a community choice. I would know, as I submitted 11 designs in that > context. What I claimed is that the **current** logo was not chosen by > a community process. As the **current** logo was NOT the winning logo. > The winning logo (actually four) was a single, or trio, of stacked > cards (see attached). And as you can see it is very different from > what we have now. I am confused. The winning logo is the beehive design by Zoltan Juhasz https://en.m.wikipedia.org/wiki/File:Boost.png I should know, I tallied the votes. I have no idea what that design you attached is. Regards, -- Joel de Guzman Cycfi Research, Inc.

3 3

Re: [boost] New Logo Discussion
by René Ferdinand Rivera Morell 18 Jul '24

18 Jul '24

On Wed, Jul 17, 2024 at 8:36 PM René Ferdinand Rivera Morell <grafikrobot(a)gmail.com> wrote: > > On Wed, Jul 17, 2024 at 6:50 PM Joel de Guzman via Boost > <boost(a)lists.boost.org> wrote: > > > > On 7/18/24 3:49 AM, René Ferdinand Rivera Morell via Boost wrote: > > > On Wed, Jul 17, 2024 at 2:42 PM Robert Ramey via Boost > > > <boost(a)lists.boost.org> wrote: > > >> On 7/17/24 11:59 AM, Vinnie Falco via Boost wrote: > > >>> Hi. It is CppCon 2024 season, and the C++ Alliance is working on letting > > >>> people know all the new and exciting things happening in Boost. We're doing > > >>> this with Boost labeled conference shirts, and a beautiful brochure. You > > >>> can see a draft of this promotional piece here (note: work in progress): > > >>> > > >>> https://cppalliance.org/pdf/Boost-Brochure-CppCon-2024.pdf > > >>> > > >> FWIW - I much prefer the current logo which was developed by community > > >> inclusive process with many submissions and designs. > > > It wasn't. The logo picked by the community in that process was never > > > used. What is currently used was the result of private design between > > > the Boost Steering Committee and the artist that "won" that logo > > > contest. > > > That is not correct. I was one of the major proponents of that logo contest (if not > > spearheded it). > > And I am not a member of the Boost Steering Committee. That contest was public and was > > discussed in the Boost list. It is NOT a private design. > > > > Here's part of the discussion (I do not have time to search all): > > https://lists.boost.org/Archives/boost//2005/03/81416.php > > > > You can see clearly I was asking for votes. > > I did not claim the logo contest was not community driven and resulted > in a community choice. I would know, as I submitted 11 designs in that > context. What I claimed is that the **current** logo was not chosen by > a community process. As the **current** logo was NOT the winning logo. > The winning logo (actually four) was a single, or trio, of stacked > cards (see attached). And as you can see it is very different from > what we have now. Trying this again because the attachment was too big. :-( See pair of individual images. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

1 0

Where is Boost.Parser?
by Vinnie Falco 17 Jul '24

17 Jul '24

Boost.Parser was accepted on February 28th but it is not in the superproject, and the last commit in the source repository is from four months ago. I am developing a Boost brochure for CppCon 2024 and I'd like to go to press with Boost.Parser as a listed library, so this is a blocker. Thanks

3 5

Rephrased: Building Boost for MacOS / clang
by Stephen Greenfield 17 Jul '24

17 Jul '24

On Thu, 11 Jul 2024 Richard Hodges wrote: > This usually happens because you're compiling with one standard library > (e.g. libc++, the default on clang) while your boost libraries were > compiled with another (e.g. libstdc++, the default on gcc). I've recompiled my MacOS program for GCC (GNU C++17) and linked with libstdc++ to be compatible with the default build of Boost. Your suggestion WAS the solution to my reported slew of error messages. Thanks! QUESTION 1: But for building a standard MacOS or iPhone/iPad app, shouldn't I be building both my app and Boost for clang, so I can link with libc++? When I looked at the list of toolsets in the "getting started with unix variants", included with the 1_85_0 .zip package, there was no listing for toolset=clang or toolset=clang-darwin. Nor is there any mention of clang on: https://www.boost.org/doc/libs/1_85_0/more/getting_started/unix-variants.ht… QUESTION 2: So what is the proper toolset / build instructions to build for MacOS using the clang C++17 compiler? Stephen

1 0

A question for folks here
by David Sankel 16 Jul '24

16 Jul '24

For those who got involved in Boost within the last couple years, how did you hear about boost? What attracted you to it? For those who have been around for a while, what keeps you here? Why do you stay engaged?

16 25

[unordered] New natvis visualizations + accompanying article
by Braden Ganetsky 16 Jul '24

16 Jul '24

Hi everyone, This is my first message on the ML. I've written visualizations in the Visual Studio Natvis framework for the Boost.Unordered containers and iterators. This will improve the user experience for anyone using Visual Studio. The visualizations mirror those of the STL unordered containers as closely as possible, except that end iterators display as "{ end iterator }" instead of the visualization just breaking. Here is the file: https://github.com/boostorg/unordered/blob/develop/extra/boost_unordered.na… I've written an accompanying article about the natvis implementation for the closed-addressing containers. I will be writing a second article about the implementation for the open-addressing containers. This first article contains some tips and tricks for using the natvis framework that I wish I knew before going into this, especially about using "<Intrinsic>" elements. Hopefully it can help someone else. Link to the article: https://blog.ganets.ky/NatvisForUnordered/ Custom gdb pretty-printers will be next up. Thank you to Joaquín for reviewing the code and the article. Thanks all, Braden Ganetsky

2 2

Re: [boost] Boost Digest, Vol 7279, Issue 2
by Stephen Greenfield 15 Jul '24

15 Jul '24

BUMP / RE-SENT -- I think I got lost in a flurry of responses to another subject: Richard – > This usually happens because you're compiling with one standard library > (e.g. libc++, the default on clang) while your boost libraries were > compiled with another (e.g. libstdc++, the default on gcc). That makes sense. Does my MacOS program need to be compiled for GCC (IE GNU C++17 / GNU C++20), and then linked with libstdc++ to be compatible with the default build of Boost, or the opposite: build Boost and link with libc++? I saw that there's a list of toolsets, but in the "getting started with unix variants", included with the 1_85_0 .zip package, there is no listing for toolset=clang or toolset=clang-darwin. Nor is there any mention of clang on: https://www.boost.org/doc/libs/1_85_0/more/getting_started/unix-variants.ht… Stephen

1 0

Re: [boost] Boost Digest, Vol 7279, Issue 2
by Stephen Greenfield 11 Jul '24

11 Jul '24

Richard – > This usually happens because you're compiling with one standard library > (e.g. libc++, the default on clang) while your boost libraries were > compiled with another (e.g. libstdc++, the default on gcc). That makes sense. Does my MacOS program need to be compiled for GCC (IE GNU C++17 / GNU C++20), and then linked with libstdc++ to be compatible with the default build of Boost, or the opposite: build Boost and link with libc++? I saw that there’s a list of toolsets, but in the “getting started with unix variants”, included with the 1_85_0 .zip package, there is no listing for toolset=clang or toolset=clang-darwin. Nor is there any mention of clang on: https://www.boost.org/doc/libs/1_85_0/more/getting_started/unix-variants.ht… Stephen -- ------------------------------ Message: 5 Date: Thu, 11 Jul 2024 09:43:01 +0200 From: Richard Hodges <hodges.r(a)gmail.com> To: boost(a)lists.boost.org Subject: Re: [boost] Updating from 1_71_0 to 1_85_0: "No member named 'memcpy' in namespace 'std::__1'" Message-ID: <CALvx3haD3uRR4sXjjDq5Hrw4XoTq11HMqQyq2D5taJQzH7ys7A(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" This usually happens because you're compiling with one standard library (e.g. libc++, the default on clang) while your boost libraries were compiled with another (e.g. libstdc++, the default on gcc). R On Thu, 11 Jul 2024 at 02:21, Stephen Greenfield via Boost < boost(a)lists.boost.org> wrote: > Dear Boost gurus, > > Building on MacOS 12.7.3, Xcode 13.4.1, C++ dialect = C++17. Deployment > target is 10.15. This particular project is x86_64 architecture. I?m only > linking libboost_filesystem.a and libboost_iostreams.a (I show my build > boost build steps at the end). > > When updating from Boost 1_71_0 to 1_85_0, I?m suddenly encountering these > kinds of errors: > > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__functional/hash.h:40:5: > No member named 'memcpy' in namespace 'std::__1'; did you mean simply > 'memcpy'? > > > /Users/stephen/dev/Boost > Libraries/boost_1_85_0/boost/system/detail/append_int.hpp:23:5: No member > named 'snprintf' in namespace 'boost::system::detail'; did you mean simply > 'snprintf'? > > > > > In file included from > /Users/stephen/dev/Screenwriter/ScreenWriterX/ScreenWriterX/Screenwriter > Sources/Text Engine/CThingEdit.cp:22: > > In file included from ../ScreenWriterX/ScreenWriterX/Screenwriter > Sources/Text Engine/CThingEdit.h:61: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/string:522: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/algorithm:653: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/functional:500: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__functional/function.h:20: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__memory/shared_ptr.h:25: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__memory/unique_ptr.h:15: > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__functional/hash.h:40:5: > error: no member named 'memcpy' in namespace 'std::__1'; did you mean > simply 'memcpy'? > > _VSTD::memcpy(&__r, __p, sizeof(__r)); > > ^~~~~~~ > > In file included from <built-in>:1: > > In file included from > /Users/stephen/dev/Screenwriter/ScreenWriterX/ScreenWriterX/Screenwriter > Sources/Screenwriter_Prefix.pch:505: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/MacTypes.h:44: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/stdbool.h:22: > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__config:858:15: > note: expanded from macro '_VSTD' > > #define _VSTD std::_LIBCPP_ABI_NAMESPACE > > ^ > > In file included from > /Users/stephen/dev/Screenwriter/ScreenWriterX/ScreenWriterX/Screenwriter > Sources/Text Engine/CThingEdit.cp:22: > > In file included from ../ScreenWriterX/ScreenWriterX/Screenwriter > Sources/Text Engine/CThingEdit.h:61: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/string:522: > > In file included from > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/algorithm:652: > > /Users/stephen/dev/Boost > Libraries/boost_1_85_0/boost/compatibility/cpp_c_headers/cstring:22:11: > note: 'memcpy' declared here > > using ::memcpy; > > ^ > ?this is for all sorts of symbols. ALSO: > > > > > Showing All Errors Only > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/filesystem:2635:5: > Use of undeclared identifier '_LIBCPP_UNREACHABLE' > > > When including: > > #include <fstream> > > > The libraries were build using: > > ./bootstrap.sh cxxflags="-arch x86_64 -arch arm64" cflags="-arch x86_64 > -arch arm64" linkflags="-arch x86_64 -arch arm64" > > ./b2 toolset=clang-darwin target-os=darwin architecture=arm abi=aapcs > cxxflags="-arch arm64" cflags="-arch arm64" linkflags="-arch arm64" -a > > mkdir -p arm64 && cp stage/lib/*.* arm64 > > ./b2 toolset=clang-darwin target-os=darwin architecture=x86 > cxxflags="-arch x86_64" cflags="-arch x86_64" linkflags="-arch x86_64" > abi=sysv binary-format=mach-o -a > > mkdir x86_64 && cp stage/lib/*.* x86_64 > > The intention was for me to eventually make UNIVERSAL dylibs using lipo ? > but for now, I just want to get my build back to functioning with Boost > 1_85_0. > > NOTE that I?m continuing to use Boost?s Filesystem ? even though I THINK > Xcode?s C++20 might now support std::filesystem. > > I?ve searched all over for the answer ? even consulted ChatGPT ? but > haven?t found a solution. But this seems like something bone-headed I?ve > missed. > > Stephen > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost > ------------------------------ Subject: Digest Footer _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost ------------------------------ End of Boost Digest, Vol 7279, Issue 2 **************************************

1 0

Updating from 1_71_0 to 1_85_0: "No member named 'memcpy' in namespace 'std::__1'"
by Stephen Greenfield 11 Jul '24

11 Jul '24

Dear Boost gurus, Building on MacOS 12.7.3, Xcode 13.4.1, C++ dialect = C++17. Deployment target is 10.15. This particular project is x86_64 architecture. I’m only linking libboost_filesystem.a and libboost_iostreams.a (I show my build boost build steps at the end). When updating from Boost 1_71_0 to 1_85_0, I’m suddenly encountering these kinds of errors: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__functional/hash.h:40:5: No member named 'memcpy' in namespace 'std::__1'; did you mean simply 'memcpy'? /Users/stephen/dev/Boost Libraries/boost_1_85_0/boost/system/detail/append_int.hpp:23:5: No member named 'snprintf' in namespace 'boost::system::detail'; did you mean simply 'snprintf'? In file included from /Users/stephen/dev/Screenwriter/ScreenWriterX/ScreenWriterX/Screenwriter Sources/Text Engine/CThingEdit.cp:22: In file included from ../ScreenWriterX/ScreenWriterX/Screenwriter Sources/Text Engine/CThingEdit.h:61: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/string:522: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/algorithm:653: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/functional:500: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__functional/function.h:20: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__memory/shared_ptr.h:25: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__memory/unique_ptr.h:15: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__functional/hash.h:40:5: error: no member named 'memcpy' in namespace 'std::__1'; did you mean simply 'memcpy'? _VSTD::memcpy(&__r, __p, sizeof(__r)); ^~~~~~~ In file included from <built-in>:1: In file included from /Users/stephen/dev/Screenwriter/ScreenWriterX/ScreenWriterX/Screenwriter Sources/Screenwriter_Prefix.pch:505: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/MacTypes.h:44: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/stdbool.h:22: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/__config:858:15: note: expanded from macro '_VSTD' #define _VSTD std::_LIBCPP_ABI_NAMESPACE ^ In file included from /Users/stephen/dev/Screenwriter/ScreenWriterX/ScreenWriterX/Screenwriter Sources/Text Engine/CThingEdit.cp:22: In file included from ../ScreenWriterX/ScreenWriterX/Screenwriter Sources/Text Engine/CThingEdit.h:61: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/string:522: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/algorithm:652: /Users/stephen/dev/Boost Libraries/boost_1_85_0/boost/compatibility/cpp_c_headers/cstring:22:11: note: 'memcpy' declared here using ::memcpy; ^ …this is for all sorts of symbols. ALSO: Showing All Errors Only /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/include/c++/v1/filesystem:2635:5: Use of undeclared identifier '_LIBCPP_UNREACHABLE' When including: #include <fstream> The libraries were build using: ./bootstrap.sh cxxflags="-arch x86_64 -arch arm64" cflags="-arch x86_64 -arch arm64" linkflags="-arch x86_64 -arch arm64" ./b2 toolset=clang-darwin target-os=darwin architecture=arm abi=aapcs cxxflags="-arch arm64" cflags="-arch arm64" linkflags="-arch arm64" -a mkdir -p arm64 && cp stage/lib/*.* arm64 ./b2 toolset=clang-darwin target-os=darwin architecture=x86 cxxflags="-arch x86_64" cflags="-arch x86_64" linkflags="-arch x86_64" abi=sysv binary-format=mach-o -a mkdir x86_64 && cp stage/lib/*.* x86_64 The intention was for me to eventually make UNIVERSAL dylibs using lipo – but for now, I just want to get my build back to functioning with Boost 1_85_0. NOTE that I’m continuing to use Boost’s Filesystem – even though I THINK Xcode’s C++20 might now support std::filesystem. I’ve searched all over for the answer – even consulted ChatGPT – but haven’t found a solution. But this seems like something bone-headed I’ve missed. Stephen

4 3

Re: [boost] A question for folks here
by me＠kennethreitz.org 11 Jul '24

11 Jul '24

Hi all, My name is Kenneth Reitz, and I got involved with Boost when Vinnie Falco asked me to join the C++ Alliance to work on the new boost website. You might recognize my name from the Python community, where I’m known for making Requests, Pipenv, and other tools. It’s nice to meet everyone! — Kenneth Reitz > 1. A question for folks here (David Sankel) > 2. Re: A secure string library? (Andrey Semashev) > 3. Re: A secure string library? (Andrey Semashev) > 4. Re: A question for folks here (Richard Hodges) > 5. Re: A secure string library? (Daniela Engert) > 6. Re: A secure string library? (Andrey Semashev) > 7. Re: A secure string library? (Christian Mazakas) > 8. Re: A question for folks here (Matt Borland) > 9. Re: A question for folks here (Christopher Kormanyos) > 10. Re: A question for folks here (Louis Tatta) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 10 Jul 2024 10:47:50 -0400 > From: David Sankel <camior(a)gmail.com> > To: Boost <boost(a)lists.boost.org> > Subject: [boost] A question for folks here > Message-ID: > <CAFYdOO+m95fKjxnKY3SY_eHC-X=PLs12BteaONG+QpS6fTCxcQ(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > For those who got involved in Boost within the last couple years, how did > you hear about boost? What attracted you to it? > > For those who have been around for a while, what keeps you here? Why do you > stay engaged? > > > ------------------------------ > > Message: 2 > Date: Wed, 10 Jul 2024 18:26:20 +0300 > From: Andrey Semashev <andrey.semashev(a)gmail.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] A secure string library? > Message-ID: <6265cabd-c0b9-405e-98f4-8a47683e5472(a)gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 7/10/24 14:59, Peter Dimov via Boost wrote: >> Ruben Perez wrote: >>> There is OPENSSL_Cleanse, which does a similar job. I found it surprisingly >>> simple - I wonder if this is just enough or there are any corner cases where this >>> doesn't work: >>> https://github.com/openssl/openssl/blob/b544047c99c4a7413f793afe82ab1c165f8… >> >> That's an interesting approach. I can't offhand think of a reason why it wouldn't >> work. > > The compiler might convert OPENSSL_cleanse to something like this: > > void OPENSSL_cleanse(void *ptr, size_t len) > { > memset_t func = memset_func; > if (func != memset) > func(ptr, 0, len); > else > memset(ptr, 0, len); > } > > The purpose here is that, if memset_func is actually memset most of the > time, it can further optimize the call to memset, including to > completely remove it, depending on the call context. The > (well-predictable) branch is typically cheaper than an indirect call. I > think I've seen compilers do something along those lines as a result of > call devirtualization, especially with IPO and LTCG. > > I'm not saying that's what actually happens in OpenSSL, just that > something like this is possible. I think, a dummy asm statement is more > reliable and more efficient. > > void secure_cleanse(void *ptr, size_t len) > { > memset(ptr, 0, len); // a normal memset, optimizations are welcome > __asm__ __volatile__ ("" : : "r" (ptr), "r" (len) : "memory"); > } > > You can even make that function inline and it'll work, and in an optimal > way, too. > > > > ------------------------------ > > Message: 3 > Date: Wed, 10 Jul 2024 18:37:00 +0300 > From: Andrey Semashev <andrey.semashev(a)gmail.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] A secure string library? > Message-ID: <57326885-13ab-4a73-ac5a-5aa6357e799c(a)gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 7/10/24 18:26, Andrey Semashev wrote: >> On 7/10/24 14:59, Peter Dimov via Boost wrote: >>> Ruben Perez wrote: >>>> There is OPENSSL_Cleanse, which does a similar job. I found it surprisingly >>>> simple - I wonder if this is just enough or there are any corner cases where this >>>> doesn't work: >>>> https://github.com/openssl/openssl/blob/b544047c99c4a7413f793afe82ab1c165f8… >>> >>> That's an interesting approach. I can't offhand think of a reason why it wouldn't >>> work. >> >> The compiler might convert OPENSSL_cleanse to something like this: >> >> void OPENSSL_cleanse(void *ptr, size_t len) >> { >> memset_t func = memset_func; >> if (func != memset) >> func(ptr, 0, len); >> else >> memset(ptr, 0, len); >> } >> >> The purpose here is that, if memset_func is actually memset most of the >> time, it can further optimize the call to memset, including to >> completely remove it, depending on the call context. The >> (well-predictable) branch is typically cheaper than an indirect call. I >> think I've seen compilers do something along those lines as a result of >> call devirtualization, especially with IPO and LTCG. >> >> I'm not saying that's what actually happens in OpenSSL, just that >> something like this is possible. I think, a dummy asm statement is more >> reliable and more efficient. >> >> void secure_cleanse(void *ptr, size_t len) >> { >> memset(ptr, 0, len); // a normal memset, optimizations are welcome >> __asm__ __volatile__ ("" : : "r" (ptr), "r" (len) : "memory"); >> } >> >> You can even make that function inline and it'll work, and in an optimal >> way, too. > > And for compilers that don't support __asm__, I think you could replace > it with: > > std::atomic_signal_fence(std::memory_order::acq_rel); > > > > ------------------------------ > > Message: 4 > Date: Wed, 10 Jul 2024 18:01:03 +0200 > From: Richard Hodges <hodges.r(a)gmail.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] A question for folks here > Message-ID: > <CALvx3hYSO6svxz_aEw_LoaraweTguqW+jJScTyfymZAveOrXZg(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Wed, 10 Jul 2024 at 16:48, David Sankel via Boost <boost(a)lists.boost.org> > wrote: > >> For those who got involved in Boost within the last couple years, how did >> you hear about boost? What attracted you to it? >> > > I've been using boost as an essential force multiplier of C++ since version > 1.35 when Asio appeared, courtesy of Chris Kohlhoff. > > More recently in 2017, I needed an asynchronous websocket library for C++ > and lo-and-behold, boost had one, courtesy of Vinnie Falco. > > >> >> For those who have been around for a while, what keeps you here? Why do you >> stay engaged? >> > > After finishing a contract in which I used Boost.Beast et.al. in production > code, I took up an offer by the C++ Alliance to become a maintainer of it. > A bit of a "Victor Kiam" moment, if you will. > > While working for the C++ Alliance I was also involved in the design and > first cut of Boost.Json and had some input into Boost.Url, another two very > keenly needed libraries sponsored by the C++ Alliance. > I am no longer working for the C++ Alliance, but maintain a warm > relationship with the organisation. > > I am currently using Boost.Cobalt in a financial trading software suite. > > I stay engaged because: > - I don't want to have to switch languages - C++ is perfectly fine for me. > - Boost polyfills all the essential functionality that the children running > WG21 continue to refuse to provide. > - It's convenient to have one library that provides (almost) every tool I > need. > > My very great thanks to the original authors and contributors, and more > recently to the C++ Alliance, which as far as I can see is the only major > sponsor of Boost. > Without this organisation's involvement, I believe the libraries would have > been allowed to fall into disrepair a long time ago. > > I don't think I have met more than one team in the financial industry which > uses C++ but which does not use Boost. > > On a separate note, I was deeply disappointed by your recent public > outbursts, David. > > Sincerely, > > Richard Hodges > A C++phile > ex maintainer of Boost.Beast > contributor to Boost.Json, Boost.Url > Advisor to Boost.MySQL, Boost.Cobalt > > >> >> _______________________________________________ >> Unsubscribe & other changes: >> http://lists.boost.org/mailman/listinfo.cgi/boost >> > > > ------------------------------ > > Message: 5 > Date: Wed, 10 Jul 2024 18:13:41 +0200 > From: Daniela Engert <dani(a)ngrt.de> > To: boost(a)lists.boost.org > Subject: Re: [boost] A secure string library? > Message-ID: <98140e71-ef1e-431a-a089-e24f56e390bd(a)ngrt.de> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Am 10.07.2024 um 17:37 schrieb Andrey Semashev via Boost: >> On 7/10/24 18:26, Andrey Semashev wrote: >>> On 7/10/24 14:59, Peter Dimov via Boost wrote: >>>> Ruben Perez wrote: >>>>> There is OPENSSL_Cleanse, which does a similar job. I found it surprisingly >>>>> simple - I wonder if this is just enough or there are any corner cases where this >>>>> doesn't work: >>>>> https://github.com/openssl/openssl/blob/b544047c99c4a7413f793afe82ab1c165f8… >>>> That's an interesting approach. I can't offhand think of a reason why it wouldn't >>>> work. >>> The compiler might convert OPENSSL_cleanse to something like this: >>> >>> void OPENSSL_cleanse(void *ptr, size_t len) >>> { >>> memset_t func = memset_func; >>> if (func != memset) >>> func(ptr, 0, len); >>> else >>> memset(ptr, 0, len); >>> } >>> >>> The purpose here is that, if memset_func is actually memset most of the >>> time, it can further optimize the call to memset, including to >>> completely remove it, depending on the call context. The >>> (well-predictable) branch is typically cheaper than an indirect call. I >>> think I've seen compilers do something along those lines as a result of >>> call devirtualization, especially with IPO and LTCG. >>> >>> I'm not saying that's what actually happens in OpenSSL, just that >>> something like this is possible. I think, a dummy asm statement is more >>> reliable and more efficient. >>> >>> void secure_cleanse(void *ptr, size_t len) >>> { >>> memset(ptr, 0, len); // a normal memset, optimizations are welcome >>> __asm__ __volatile__ ("" : : "r" (ptr), "r" (len) : "memory"); >>> } >>> >>> You can even make that function inline and it'll work, and in an optimal >>> way, too. >> And for compilers that don't support __asm__, I think you could replace >> it with: >> >> std::atomic_signal_fence(std::memory_order::acq_rel); >> > I think Peter is actually right in his assessment: > > While 'memset_func' is TU-local, it is also 'volatile'. This implies > every look at it might reveal a different content. Therefore the > necessity for non-constness and dynamic initialization. We humans see > that the variable can't change its value other than in the > initialization. The compiler can't reason that because said properties > are the only ones known during the compilation of 'OPENSSL_cleanse()'. > It can't perform unbounded look-ahead until the end of the TU like we do. > > Dani > > -- > PGP/GPG: 2CCB 3ECB 0954 5CD3 B0DB 6AA0 BA03 56A1 2C4638C5 > > ------------------------------ > > Message: 6 > Date: Wed, 10 Jul 2024 19:24:48 +0300 > From: Andrey Semashev <andrey.semashev(a)gmail.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] A secure string library? > Message-ID: <905dd5f7-5d29-48ab-87aa-6aa0a23e60c6(a)gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 7/10/24 19:13, Daniela Engert via Boost wrote: >> Am 10.07.2024 um 17:37 schrieb Andrey Semashev via Boost: >>> On 7/10/24 18:26, Andrey Semashev wrote: >>>> On 7/10/24 14:59, Peter Dimov via Boost wrote: >>>>> Ruben Perez wrote: >>>>>> There is OPENSSL_Cleanse, which does a similar job. I found it >>>>>> surprisingly >>>>>> simple - I wonder if this is just enough or there are any corner >>>>>> cases where this >>>>>> doesn't work: >>>>>> https://github.com/openssl/openssl/blob/b544047c99c4a7413f793afe82ab1c165f8… >>>>> That's an interesting approach. I can't offhand think of a reason >>>>> why it wouldn't >>>>> work. >>>> The compiler might convert OPENSSL_cleanse to something like this: >>>> >>>> ?? void OPENSSL_cleanse(void *ptr, size_t len) >>>> ?? { >>>> ???? memset_t func = memset_func; >>>> ???? if (func != memset) >>>> ?????? func(ptr, 0, len); >>>> ???? else >>>> ?????? memset(ptr, 0, len); >>>> ?? } >>>> >>>> The purpose here is that, if memset_func is actually memset most of the >>>> time, it can further optimize the call to memset, including to >>>> completely remove it, depending on the call context. The >>>> (well-predictable) branch is typically cheaper than an indirect call. I >>>> think I've seen compilers do something along those lines as a result of >>>> call devirtualization, especially with IPO and LTCG. >>>> >>>> I'm not saying that's what actually happens in OpenSSL, just that >>>> something like this is possible. I think, a dummy asm statement is more >>>> reliable and more efficient. >>>> >>>> ?? void secure_cleanse(void *ptr, size_t len) >>>> ?? { >>>> ???? memset(ptr, 0, len); // a normal memset, optimizations are welcome >>>> ???? __asm__ __volatile__ ("" : : "r" (ptr), "r" (len) : "memory"); >>>> ?? } >>>> >>>> You can even make that function inline and it'll work, and in an optimal >>>> way, too. >>> And for compilers that don't support __asm__, I think you could replace >>> it with: >>> >>> ?? std::atomic_signal_fence(std::memory_order::acq_rel); >>> >> I think Peter is actually right in his assessment: >> >> While 'memset_func' is TU-local, it is also 'volatile'. This implies >> every look at it might reveal a different content. Therefore the >> necessity for non-constness and dynamic initialization. We humans see >> that the variable can't change its value other than in the >> initialization. The compiler can't reason that because said properties >> are the only ones known during the compilation of 'OPENSSL_cleanse()'. >> It can't perform unbounded look-ahead until the end of the TU like we do. > > With volatile, the compiler is not allowed to optimize away or reorder > loads and stores of the variable. There's no restriction on what the > compiler is allowed to do with the loaded value. > > > > ------------------------------ > > Message: 7 > Date: Wed, 10 Jul 2024 10:10:43 -0700 > From: Christian Mazakas <christian.mazakas(a)gmail.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] A secure string library? > Message-ID: > <CAHf7xWueD5=ekMC178pikzH2iuhAtyzC6v5UgPBSoj0NMy3y9Q(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > >> Andrey Semashev via Boost: >> With volatile, the compiler is not allowed to optimize away or reorder >> loads and stores of the variable. There's no restriction on what the >> compiler is allowed to do with the loaded value. > > It could insert a branch against `memset` but that seems really only like a > theoretical > optimization. > > This is an example where the volatile preserves the secure_erase() call: > https://godbolt.org/z/854jfarb9 > > Kind of neat trying to get the compiler to elide this stuff. You were > right, Andrey, you really need > LTO and LTCG and the like to get this kind of behavior. Super neat stuff. > > Idk, seems like whatever OpenSSL is doing is Sound Enough in practice. > > I'd be curious to know if it's actually sound for a compiler to make that > kind of optimization or at least > what are the limits on how far a compiler can actually go to ensure > soundness. If you know those limits, > you can probably make this pattern work reliably. > > - Christian > > > ------------------------------ > > Message: 8 > Date: Wed, 10 Jul 2024 17:57:57 +0000 > From: Matt Borland <matt(a)mattborland.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] A question for folks here > Message-ID: > <LQ-gmVceAUPyCRzsmP5gN1Z4NJiwrRtJ-yJY5Q6Ne-3SnJ_omC84hltKP9AbS3x-TVlz35Amln3jW0CBdG0nnzAioM53fxXobq0GO3zYb2E=(a)mattborland.com> > > Content-Type: text/plain; charset="utf-8" > > >> For those who got involved in Boost within the last couple years, how did >> you hear about boost? > > I heard about it from a university professor as a freshman undergraduate student in 2011. Since C++11 was just coming about, and the speed of updating toolchains in academia is slow so we were stuck in the C++03 days on old RHEL systems. > >> What attracted you to it? > > I was studying aeronautical engineering so having pre-made libraries like Boost.Math, Boost.Multiprecision, and ODEint were useful to me. I could focus on the problem at hand rather than having to roll my own special functions, solvers, big numbers, constants, etc. > >> For those who have been around for a while, what keeps you here? Why do you stay engaged? > > I started to get involved with development during the COVID lockdowns because like many people I found myself with quite a bit of extra free time. What hooked me was learning from and working with extremely competent programmers and mathematicians like John Maddock, Chris Kormanyos, and Nick Thompson. I was hired by the C++ Alliance at the beginning of 2023 and they have sponsored my development since. This allows me to work on new (https://github.com/cppalliance/decimal) and existing libraries (charconv, math, multiprecision, random, etc) in a way that I was never able to on a volunteer basis with a full time job. The community is large, knowledgeable, and helpful so I continue to enjoy working on Boost. > > > I think it would be beneficial to the developer community for the Boost Foundation board members to also answer these questions. Frankly some even require introductions with their answers. There are members of the board like Peter, Glen, and Zach that are Titans of Boost, and those like Kristen who I had not heard of until her post about wanting to cut ties with the C++ Alliance. Having unknown members of the Boost Foundation runs counter to their mission statement whereby the board intends to achieve its mission by "fostering community engagement, [and] nurturing leaders..."[1]. > > Matt > > [1] https://sites.google.com/boost.org/boost-foundation/home >

2 1

A secure string library?
by Ruben Perez 10 Jul '24

10 Jul '24

Hi all, Boost.MySQL and Boost.Redis need to hold sensitive information, like passwords, to work. Using std::string may be sufficient for many use cases, but it's not the best security practice. std::string doesn't wipe its memory on cleanup, resulting in the password remaining in memory for an indeterminate amount of time. Other languages like C# implement a SecureString class that wipes memory on destruction. Crypto++ implements a similar concept, but it's a big dependency I'm not willing to take. I'd like to know whether everyone else's opinion on this: * Have you faced this issue before? * Do you think this is something we (as Boost authors) should care about, or am I thinking too much? * Do you think a library implementing secure string/array/buffer classes would be a valuable addition to Boost? Thanks, Ruben.

11 22

[boost 1.85.0 MSVC142-64 ]type_name.hpp(354,2): error C2766: explicit specialization; 'boost::core::detail::tn_holder<unsigned short>' has already been defined
by Bhuyan, Jyotideep 10 Jul '24

10 Jul '24

Hello, I am updating my code from boost version 1.78 to boost 1.85. and facing build issues "error C2766: explicit specialization; 'boost::core::detail::tn_holder<unsigned short>' has already been defined" Below is the error that I am facing that needs your help. I could not find any code or direct header file inclusion in my code related to the below error. C:\<my boost>\boost_1_85\boost\boost\core\type_name.hpp(354,2): error C2766: explicit specialization; 'boost::core::detail::tn_holder<unsigned short>' has already been defined. C:\<my boost>\boost_1_85\boost\boost\core\type_name.hpp(273): message : see previous definition of 'tn_holder<unsigned short> Please note that after upgrading to boost 1.85, the compiler was not able to find "#include <boost/function/detail/prologue.hpp>", I checked this file is not present in the new version. Hence, I have commented header file inclusion in my code. I am building the code for MSVC142 (C++14) for 64-bit Windows 10 architecture. Best Regards, Jyotideep (JD) Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment. Confidential - Company Proprietary

3 2

failure to produce PDF documentation
by Robert Ramey 10 Jul '24

10 Jul '24

For many years, I've been using the xslt based system for converting boostbook xml into html an pdf files. Once I got it set up, I've never had a problem. But now, it is failing with some error messages provoked by the contents of some xml files which are part of boost book. A casual review of the correspondng github repository shows the that the some of these files have been "maintained" recently ... some as recently as 3 days ago. Could someone (probably the maintainer) look into this. I noticed that when I try to appy this to the safe numerics library. The following should reproduce the problem: cd /Users/robertramey/WorkingProjects/modular-boost/libs/safe_numerics/doc/boostbook $ls *.sh makeepub.sh makehtml.sh makepdf.sh makeproposal.sh $echo $PATH /Volumes/public/fop-2.1:.:/Volumes/public/menu_bash:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin $./makepdf.sh [Fatal Error] docbook.xsl:6:3: The element type "hr" must be terminated by the matching end-tag "</hr>". http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl; Line #6; Column #3; org.xml.sax.SAXParseException; systemId: http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl; lineNumber: 6; columnNumber: 3; The element type "hr" must be terminated by the matching end-tag "</hr>". Jul 09, 2024 2:58:38 PM org.apache.fop.cli.Main startFOP SEVERE: Exception ... Thanks to whoever looks into this. Robert Ramey

2 3

Boost 1.85, Windows, VS2022 17.10.3, build does not create any libs on building boost
by Dennis Luehring 09 Jul '24

09 Jul '24

my system Windows 10 x64, VS2022 10.7.3 Download: https://archives.boost.io/release/1.85.0/source/boost_1_85_0.7z unpack zip to boost_1_85_0 in console: cd boost_1_85_0 bootstrap.bat b2 -j%NUMBER_OF_PROCESSORS% toolset=msvc-14.3 address-model=64 --stagedir=.\lib64-msvc-14.3 --build-dir=.\__build --build-type=complete threading=multi architecture=x86 stage --with-date_time --with-graph --with-nowide --with-test --width-config --with-system --with-filesystem --with-serialization --with-locale --with-log result - lib64-msvc-14.3\lib\cmake gets created - but no libs that is my default build style up to 1.84 the output of bootstrap.bat https://pastebin.com/DQUVe3QR the output of b2 run https://pastebin.com/sJqGLDE7 it seems that all libs are ignored someway any idea?

2 2

[release] Master branch closes for the 1.86.0 beta release on WEDNESDAY
by Marshall Clow 08 Jul '24

08 Jul '24

Calendar is here: https://www.boost.org/development/ — The Release Managers

1 0

New Boost website ready for launch
by Joaquin M López Muñoz 06 Jul '24

06 Jul '24

Hi everyone, As most of you know, the new Boost website has been in the works for quite a long time: last week we've fixed the last showstopper issues and are now in a position to launch it publicly and announce to the wider community! See the launch-ready website at: https://boost.io The new website is ready to replace the current one at boost.org any time we want. The old site has served us well for 25 years, and it deserves to be given a retirement permit. OVERVIEW The new website is organized in five top-level sections: * News: an aggregator of internal announcements, blog articles, videos, etc. related to the Boost project. * Learn: comprehensive and completely rewritten tutorials and reference material for users, contributors and review participants. Check this out: there's a ton of new stuff here. * Community: links to the various discussion venues for Boost (mailing lists, Slack groups, X, etc.). * Libraries: revamped directory of Boost libraries, with integrated access to version-specific docs, repos, and more. * Releases: access to release notes, download binaries and source code for all Boost versions from 1.16.1 up to the current one. Users can navigate the website anonymously or log in to be able to contribute to the News section, receive notifications etc. The site uses responsive design to work on wide screens as well as your mobile device. Also, check the light and dark modes at the top-right corner :-) FEEDBACK AND FUTURE The evolution of the website does not stop here. We have quite a backlog of issues and new features registered at: https://github.com/boostorg/website-v2/issues https://github.com/boostorg/website-v2-docs/issues But we're also expecting your feedback! Please let us know what you think of the website and ways to improve it. I will personally make sure that all comments and suggestions are properly addressed. Ways to contribute: * Through the mailing list or the #boost-website group at cpplang.slack.com. * Filing issues directly at https://github.com/boostorg/website-v2 (website proper) and https://github.com/boostorg/website-v2 (learning material). * Learning material has an "Edit this page" link from where you can fork any documentation section and propose changes through a pull request. * Reach out to me anyway you'd like. ACKNOWLEDGEMENTS There are just too many individuals to list here who had contributed to the new website --my thanks to all of them. Let me mention some of the people I have worked with the most in the last two months, when I took over the PM role for this launch effort. * The people at REVSYS (Frank Wiles, Lacey Henschel) and Spencer Strickland built the Django-based backend and most of the frontend. Kenneth Reitz and Julio C. Estrada have been working tirelessly to close functionality gaps and fix remaining issues up to launch status. * Peter Turcan is the main author of the new learning material featured in the website. Again, check it out and help us spot glitches or propose new topics to work on. * Sam Darwin, who's already the Atlas upon whom the current Boost infrastructure rests, has double down on his responsibilites to set up and take care of this new backend. * René Rivera wrote many of the scripts that power the old website and has assisted us in the migration process with his expertise and unique insights into the particulars of Boost internal procedures. * Many people have filed issues during development, but the record holder is Andrey Semashev (39 tickets and counting). His suggestions and active involvement in the fixing process have made the website a better place. Best, Joaquín M López Muñoz

5 8

[release] The 1.86.0 release will close for major changes WEDNESDAY
by Marshall Clow 02 Jul '24

02 Jul '24

Calendar here: https://www.boost.org/development/ Next deadline: The master branch will close for the beta next Wednesday. — The release managers

3 2

1.86 release
by Andrey Semashev 01 Jul '24

01 Jul '24

Hi, Are we behind the 1.86 release schedule?

3 3

In Response to Mr. Falco's June 2024 Letter
by Kristen Shaker 01 Jul '24

01 Jul '24

Hello Boost Community, My name is Kristen. Admittedly, I am not the most active participant on the boost mailing list. However, I do serve on the Boost Foundation Board of Directors as Board Chair. It is lovely to e-meet you; Hopefully I'll have the opportunity to get to know you better during the course of my tenure. Recently, we became aware of a letter that was circulated to the Boost developer community. The Boost Foundation Board of Directors have penned the following note in response to that letter. _____________________________________ Dear Boost Community Members, Recently, Mr. Falco distributed a letter indicating intent to a) rescind his offer of hosting a new boost.org website, b) retract his agreement to retire the @BoostLibraries account on X in favor of the established @Boost_Libraries, c) create a new set of Boost mailing lists on boost.io, and d) attempt to purchase the boost.org domain name from Beman Dawes’s estate. While we are surprised and saddened by this turn of events, we agree with Mr. Falco that cutting ties between the C++ Alliance and the Boost Foundation is in everyone’s best interests. That being said, we want to acknowledge Mr. Falco and his employees’ tremendous contributions toward a modernized Boost website and significant investment in maintaining and extending the Boost Libraries. On March 28th, 2024, the Foundation voted to point the boost.org domain name at Mr. Falco’s new site. Given that we had every intention to move forward we were shocked to hear that Mr Falco felt we were “holding [his] work hostage.” The Boost Foundation was entirely unaware of Mr. Falco’s attempts to purchase the boost.org domain name. We were not consulted until it became clear to Mr. Falco that to proceed with the transaction, he would need the login credentials for the domain name provider. At that point, Mr. Falco did contact a board member requesting the credentials, which were not provided to him. We were hesitant to discuss these events publicly, but since Mr. Falco has openly described his attempts to purchase the boost.org domain name, this public response seems appropriate. The fact that he took these steps without coordinating with—or even notifying— the Boost Foundation, has shaken our confidence in the Alliance and Mr. Falco. While we very much appreciate Mr. Falco's financial investment, nonprofits like Boost are not—nor should they be—beholden to their largest financial contributors. We are committed to continuing to foster a collaborative environment where C++ developers can contribute great ideas to the open source community. Boost's consensus-based process is not always the fastest way to the best result, but it is consistent with that commitment. Ideally, Mr. Falco would be interested in contributing financially to a worthy cause without assuming control over the Libraries, but his letter indicates otherwise. Therefore, we agree with Mr. Falco’s assessment that there is no viable path forward for further coordination between The C++ Alliance and The Boost Foundation. We do, however, wish Mr. Falco and the Alliance all the best in their continued efforts to improve the C++ ecosystem. Sincerely, The Boost Foundation Board of Directors

13 16

boost::any_cast gives build errors with VS2022, boost v1.82 and C++17
by Bhuyan, Jyotideep 01 Jul '24

01 Jul '24

Hi, I was using VS2019, boost v1.78, and C++14 version and the below code was working well. Same code gives build error with VS2022, boost v1.82, and C++17 due to "o << *boost::any_cast<T>(&a); " Instruction. I wanted to know why it behaves differently. Code : class any_out { struct streamer { virtual void print(std::ostream& o, const boost::any& a) = 0; virtual streamer* clone() = 0; virtual ~streamer() {} }; public: any_out() : m_streamer(nullptr) { } ~any_out() { delete m_streamer; } template <typename T> any_out(const T& value) : m_streamer(new streamer_imp<T>), m_object(value) { } any_out(const any_out& a) : m_streamer(a.m_streamer ? a.m_streamer->clone() : nullptr), m_object(a.m_object) { } template <typename T> any_out& operator=(const T& r) { any_out(r).swap(*this); return *this; } any_out& operator=(const any_out& r) { any_out(r).swap(*this); return *this; } any_out& swap(any_out& r) noexcept { std::swap(m_streamer, r.m_streamer); std::swap(m_object, r.m_object); return *this; } friend std::ostream& operator<<(std::ostream& o, const any_out& a) { if(a.m_streamer) { a.m_streamer->print(o, a.m_object); } return o; } boost::any& get() { return m_object; } const boost::any get()const { return m_object; } bool empty() const { return m_object.empty(); } private: template <typename T> struct streamer_imp : public streamer { virtual void print(std::ostream& o, const boost::any& a) { try { if (a.empty()) { o << "<empty>"; } else { o << *boost::any_cast<T>(&a); } } } virtual streamer* clone() { return new streamer_imp<T>(); } }; // Members streamer* m_streamer; boost::any m_object; }; I have migrated to VS2022, boost v1.82, and C++17, and due to a build error, I have changed the code below. virtual void print(std::ostream& o, const boost::any& a) { try { if (a.empty()) { o << "<empty>"; } else { o << boost::any_cast<T*>(a); } } } any_out anyTest; anyTest = 100; std::string actualStr; actualStr = make_string() << anyTest; actualStr prints nullptr (0000000) instated of value 100 for VS2022, boost v1.82 and C++17 Best Regards, Jyotideep (JD) Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment. Confidential - Company Proprietary

3 3