- Boost - lists.boost.org

Reminder: Master branch is closing for the 1.83.0 beta release this WEDNESDAY (5-July)
by Marshall Clow 01 Jul '23

01 Jul '23

As always, you can find the calendar at: https://www.boost.org/development/index.html — Marshall

1 0

on windows flyweight simple_locking is using std::mutex but it should be using std::recursive_mutex()
by Foelsche, Peter 30 Jun '23

30 Jun '23

Dear All, On windows flyweight simple_locking is using std::mutex but it should be using std::recursive_mutex. I've got this firing an exception due to _Check_C_return() getting passed something else than success (number 3). I've checked by implementing my own locking policy and it definitely shows that the code is attempting to hold more than a single lock in parallel on the same mutex. The secured set.erase() can cause further flyweights to be destroyed given a suitable recursive use of flyweight. Kind Regards Peter Foelsche PS. Thanks for boost!

4 3

<stdfloat> support in Boost.Math
by Matt Borland 28 Jun '23

28 Jun '23

Today support was added for C++23’s <stdfloat> types in Boost.Math. Please let us know if you run into any warnings or errors as we go through the release captures, and betas in the following weeks. There are two common issues that we found. The first is a stack overflow in GCC 13.1 from their internal type promotion system. This will be fixed in 13.2, and we have added workarounds for it. The second are warnings and errors from implicit conversions between types. We have fixed hundreds of instances of these throughout the code base. Thank you for your help as always. Matt

1 0

Fernando Pelliccioni joins The C++ Alliance
by Vinnie Falco 28 Jun '23

28 Jun '23

I am pleased to announce that Fernando Pelliccioni has joined The C++ Alliance to become a full time contributor to Boost. This brings us to a total of 10 Staff Engineers working in C++, and 4 staff doing other work. -- Regards, Vinnie Follow me on GitHub: https://github.com/vinniefalco

1 0

Regarding the MySQL and Redis formal reviews
by Vinnie Falco 28 Jun '23

28 Jun '23

Dear All, This is a brief update on some pertinent developments. Foremost, I want to acknowledge the exceptional contributions of Ruben Perez, creator of Boost.MySQL, and Marcelo Silva, the author of Boost.Redis. Their hard work in developing and refining their respective Boost libraries exemplifies the best qualities of authorship. They are actively engaged in the various channels of the public C++ Slack Workspace (https://cppalliance.org/slack/) collaborating and answering questions. Consider joining. To clarify a potential misunderstanding, Ruben joined the C++ Alliance team only after his library Boost.MySQL was accepted. Therefore, his subsequent affiliation had no bearing on the outcome of the review. Regarding Marcelo, he has always worked independently on Boost.Redis and has no contractual relationship with The C++ Alliance. Next, I'd like to laud Klemens for his unwavering diligence. As the review manager for these two libraries, he operates with impartiality and independence from the C++ Alliance with no financial recompense. The C++ Alliance policies precludes any author sponsored by us from acting as a review manager for a library that we also sponsor. This policy underscores our belief and commitment to the effectiveness and integrity of the Boost Formal Review process. In conclusion, our objective has always remained consistent: to fortify and expand Boost, and to support the author and maintainer community. The talent, dedication, and hard work invested in making Boost the best it can be is truly commendable. Our motivation is driven by passion for the language and open source. Together, we can make Boost even more remarkable. Yours sincerely, Vinnie

1 0

Reminder: The deadline for "major changes" for Boost 1.83 is TOMORROW, 6/28
by Marshall Clow 28 Jun '23

28 Jun '23

As always, you can find the calendar at: https://www.boost.org/development/index.html — Your friendly release manager

1 0

Adding Search Functionality to boost.org
by Mohammad Nejati [ashtum] 27 Jun '23

27 Jun '23

Hey everyone, One of the issues with the current Boost website is the absence of search functionality. This forces users to rely on search engines and use queries like `site:boost.org asio cancellation_slot` However, this approach has several problems. Firstly, it often displays outdated versions in the search results. Secondly, it lacks a proper hierarchical presentation to effectively guide users. Moreover, there is no way to filter the results for a specific library. To address this problem quickly, we have decided to create a search index for the existing HTML documents on the Boost website. However, we encountered a primary challenge during this process. We needed to extract contents with the correct hierarchy for each library to ensure that the search results were displayed in a hierarchical manner. For instance, the results will be shown as `Asio › Reference › Deferred_values › Requirements` This hierarchical presentation can significantly enhance the user experience. The Boost libraries utilize various documentation formats such as QuickBook, AsciiDoc, Doxygen, and even multiple handwritten formats. This diversity posed a challenge in creating a generic crawler script. To overcome this obstacle, we initiated the Boost.Gecko project. This project involved the development of 16 custom crawlers, tailored to extract search records from the 151 Boost libraries. We are currently utilizing the Algolia search platform to index search records, which offers a free plan for open-source projects. Algolia also provides a rich JavaScript library for building a search interface on the frontend. We have leveraged this library to design a customized user interface for the search box, enhancing the navigation of search results. I kindly request you try out the new search functionality by visiting the demo page at: https://cppalliance.org/boost-gecko/ and share your thoughts, suggestions, or any issues you may encounter. Your input will greatly assist us in refining the search feature and ensuring it meets the needs of our users. Please note that the drop-down for selecting a library is included to simulate the experience of being on a specific library page. Our plan is to incorporate a search button into the header of every library page, defaulted to search within that specific library. Demo page: https://cppalliance.org/boost-gecko/ Repository: https://github.com/cppalliance/boost-gecko/ Respectfully Yours, Mohammad Nejati ---- C++ Alliance Staff Engineer

5 8

conversion of csv to pdf file
by Daggumati, Rajesh 26 Jun '23

26 Jun '23

Hi Team, As per project requirement, we need to convert .csv file to pdf file. Do we have any library to convert .csv file to pdf in boost Please let me know if we have any. Regards, Rajesh D 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

1 0

Adding 'indirect_sort' to boost::algorithm
by Marshall Clow 26 Jun '23

26 Jun '23

At Boostcon last month, there was a discussion of indirect sorting algorithms to boost::algorithm. An “Indirect sort” (called 'argsort' in numpy - https://numpy.org/doc/stable/reference/generated/numpy.argsort.html) returns a sequence of indices into the collection describing how the collection can be rearranged in order to become sorted. So I created https://github.com/boostorg/algorithm/pull/117 to start down this road. (There’s clearly more that could be done here - stable_sort, partial_sort, nth_element, etc) Comments welcomed. — Marshall

6 8

Boost.Pool regression: purge_memory() causes initial size to double on subsequent allocation
by Joel Hock 21 Jun '23

21 Jun '23

951ca5725 changed malloc_need_resize() to use set_next_size(), which sets start_size in addition to setting next_size. this causes repeated use of purge_memory() to allocate 2x size after every use. as illustration: >>>>>>>>>>>>>>>>> #include <boost/pool/pool.hpp> int main() { boost::pool pool(8); for(int i = 0; i < 10; i++) { printf("%d %ld\n", i, pool.get_next_size()); pool.purge_memory(); void *ptr = pool.malloc(); (void)ptr; } } <<<<<<<<<<<<<<<<< before the commit the output is: 0 32 1 64 2 64 3 64 4 64 5 64 6 64 7 64 8 64 9 64 after the commit, the output is: 0 32 1 64 2 128 3 256 4 512 5 1024 6 2048 7 4096 8 8192 9 16384

1 0