- Boost - lists.boost.org

Upcoming aedis review
by Klemens Morgenstern 10 Jan '23

10 Jan '23

The aedis review will start in less than a week, on the 15th and last until the 24th of this month. Aedis is a Redis client library built on top of Boost.Asio that implements the latest version of the Redis communication protocol RESP3. Some of its distinctive features are * A connection class that provides high-level functions to execute Redis commands and receive server pushes concurrently. * Automatic pipelining of commands. * Support for STL containers and serialization of user-defined data types. * Low-latency: Responses can be read in their final data-structure without creating copies. Aedis links Github: https://github.com/mzimbres/aedis Documentation: https://mzimbres.github.io/aedis/ Git tag: v1.4.1 Tarball: https://github.com/mzimbres/aedis/archive/refs/tags/v1.4.1.tar.gz Redis Links: Redis: https://redis.io/ RESP3: https://github.com/redis/redis-specifications/blob/master/protocol/RESP3.md Pipelines: https://redis.io/docs/manual/pipelining/ Redis commands: https://redis.io/commands/ Running Redis: Redis can be also easily installed on your local machine, for example, on Debian run "apt install redis". You might also want to use docker https://www.docker.com/blog/how-to-use-the-redis-docker-official-image/ Please consider writing a review next week.

1 0

CMake documentation (mostly) available
by Peter Dimov 07 Jan '23

07 Jan '23

I've written a document that explains how to use CMake to build or consume Boost, at https://github.com/boostorg/cmake/blob/develop/README.md This targets users of Boost. Developer-centric documentation is also available at https://github.com/boostorg/cmake/blob/develop/developer.md This is still unfinished, but I decided to "publish" it because the portions that are present are still (hopefully) valuable.

1 0

Fwd: CircleCI Security Alert - 4 Jan 2023 - Rotate any secrets stored in CircleCI
by Marshall Clow 05 Jan '23

05 Jan '23

I received this today….. — Marshall > Begin forwarded message: > > From: CircleCI <security(a)circleci.com> > Subject: CircleCI Security Alert - 4 Jan 2023 - Rotate any secrets stored in CircleCI > Date: January 4, 2023 at 6:30:49 PM PST > To: marshall(a)idio.com > Reply-To: security(a)circleci.com > > <https://go.circleci.com/NDg1LVpNSC02MjYAAAGJHrz8WLiocAliTEINy0V4BGCeC4xesDl…> > We wanted to make you aware that we are currently investigating a security incident, and that our investigation is ongoing. We will provide you updates about this incident, and our response, as they become available. At this point, we are confident that there are no unauthorized actors active in our systems; however, out of an abundance of caution, we want to ensure that all customers take certain preventative measures to protect your data as well. > > Action request: > > Out of an abundance of caution, we strongly recommend that all customers take the following actions: > Immediately rotate any and all secrets stored in CircleCI. These may be stored in project environment variables or in contexts. > We also recommend customers review internal logs for their systems for any unauthorized access starting from December 21, 2022 through today, January 4, 2023, or upon completion of your secrets rotation. > Additionally, if your project uses Project API tokens, we have invalidated those and you will need to replace them. You can find more information on how to do that in our documentation here. <https://go.circleci.com/NDg1LVpNSC02MjYAAAGJHrz8WBmOiXzPovREibkXKh8Iqcsacum…> > > We apologize for any disruption to your work. We take the security of our systems and our customers’ systems extremely seriously. While we are actively investigating this incident, we are committed to sharing more details with customers in the coming days. > > Thank you for your urgent attention to rotating your secrets.

1 0

Aedis scheduled for review
by Mateusz Loskot 04 Jan '23

04 Jan '23

Folks, I'd like to thank Klemens Morgenstern for stepping forward and volunteering as a review manager of the Aedis library. The Aedis review will take place between the dates of January 15, 2023 - January 24, 2023 https://www.boost.org/community/review_schedule.html Please, polish your guns and look forward to receiving the start of the review announcement from Klemens. Best regards, -- Mateusz Loskot on behalf of Boost Review Wizards

4 8

Mustache scheduled for review
by Mateusz Loskot 04 Jan '23

04 Jan '23

Folks, I'd like to thank Klemens Morgenstern for volunteering as a review manager of the Mustache library, and Peter Dimov for submitting the library. The Mustache review will take place between the dates of February 5, 2023 - February 14, 2023 https://www.boost.org/community/review_schedule.html As usual, the review manager will announce the beginning of the review with details. Best regards, -- Mateusz Loskot on behalf of Boost Review Wizards

1 0

Updating Review Schedule
by Mateusz Loskot 03 Jan '23

03 Jan '23

Happy New Year Everyone! On behalf of the Review Wizards Team, I'm updating the review schedule. It looks like we will be enjoying two reviews this month yet: - Aedis by Marcelo Zimbres Silva (start planned for Jan, 15) - Mustache by Peter Dimov (start planned not too long after aedis review) Before I issue official announcements, if there are any objections to this plan, then please express them now. Best regards, Mateusz Loskot

2 2

New Boost library proposal, Mustache
by Peter Dimov 30 Dec '22

30 Dec '22

I'm looking for endorsements and a review manager volunteer for a new library, Boost.Mustache. It's an implementation of Mustache templates (http://mustache.github.io/) in C++11 and at the moment supports the mandatory portions of the Mustache spec (https://github.com/mustache/spec) The repository is https://github.com/pdimov/mustache. Mustache is a simple templating language in which tags of the form {{something}} are replaced with the value of the entity `something`, which typically means with the member "something" of the JSON object passed when rendering the template. Boost.Mustache can take a Boost.JSON object as the context against which data references are resolved, but it can also take arbitrary values that can be converted to boost::json::value by using boost::json::value_from. This allows, for instance, described classes (structs and classes annotated with Boost.Describe) to be passed as the data context, such that references to e.g. {{title}} in the template are resolved to the corresponding `title` member of the class. A simple usage example demonstrating the above is: ``` #include <boost/mustache.hpp> #include <boost/describe.hpp> #include <iostream> struct item { std::string title; std::string author; std::string link; }; BOOST_DESCRIBE_STRUCT(item, (), (title, author, link)) struct reference { std::string heading; std::vector<item> items; }; BOOST_DESCRIBE_STRUCT(reference, (), (heading, items)) int main() { reference ref = { "Reference", { { "Better Bit Mixing - Improving on MurmurHash3's 64-bit Finalizer", "David Stafford", "https://zimbry.blogspot.com/2011/09/better-bit-mixing-improving-on.html" }, { "Stronger, better, morer, Moremur; a better Murmur3-type mixer", "Pelle Evensen", "https://mostlymangling.blogspot.com/2019/12/stronger-better-morer-moremur-b…" }, { "Improved mx3 and the RRC test", "Jon Maiga", "http://jonkagstrom.com/mx3/mx3_rev2.html" } } }; std::string tmpl = R"(<html> <body> <h1>{{heading}}</h1> <ul> {{#items}} <li> {{title}} {{author}} <a href="{{link}}">{{link}}</a> {{/items}} </ul> </body> </html>)"; boost::mustache::render( tmpl, std::cout, ref, {} ); } ``` The resulting output is <html> <body> <h1>Reference</h1> <ul> <li> Better Bit Mixing - Improving on MurmurHash3's 64-bit Finalizer David Stafford <a href="https://zimbry.blogspot.com/2011/09/better-bit-mixing-improving-on.html">https://zimbry.blogspot.com/2011/09/better-bit-mixing-improving-on.html</a> <li> Stronger, better, morer, Moremur; a better Murmur3-type mixer Pelle Evensen <a href="https://mostlymangling.blogspot.com/2019/12/stronger-better-morer-moremur-b…">https://mostlymangling.blogspot.com/2019/12/stronger-better-morer-moremur-b…</a> <li> Improved mx3 and the RRC test Jon Maiga <a href="http://jonkagstrom.com/mx3/mx3_rev2.html">http://jonkagstrom.com/mx3/mx3_rev2.html</a> </ul> </body> </html>

5 5

Tribute to John Kalb
by Robert Ramey 27 Dec '22

27 Dec '22

It's the end of 2022. I wanted to take a moment to recognize the contributions to Boost over the last dozen years or so by Jon Kalb. I first met Jon at a Microsoft Meeting named "Going Native" which was promoting a "resurgence" of C++ over Languages like Java and C#. It seems that this was related to the C++ committee incorporating large parts of Boost into the standard library and Microsofts renewed commitment to C++. This is my take, I'm sure someone else could provide more details on this. My view that was that there wasn't much more for Boost to do. Dave Abrahams was moving on to bigger things which reinforced this impression. Jon was enthusiastic about taking the lead on Boost. It was clear that he and I had a different visions. I sort of cringed - it looked to me like he got suckered. He asked me if I planned to attend C++Now - I weaseled out of actually answering. Of course he turned out to be right and I was wrong. The C++ committee hasn't really been able to replace Boost. It's too slow and cumbersome. Working as a design committee isolated from actual implementation doesn't seem to conducive to designing good, clean, elegant software. And it takes forever. It's odd to me that the committee adopted a large part of Boost software, but failed to learn anything from Boost about how to make this kind of stuff. So in this environment Jon led Boost. He worked from top to bottom on all the stuff that needs to be done - finances, legal, C++Now planning, recruitment of collaborators, etcetra . Very successful and, like many successful people, made it look easy. Hence he has not been appreciated to the extent he should be. Now he as moved on from Boost - he will be missed. Apparently this was in the works for some time but was pushed along by complaint about his handling about an alleged code of conduct violation which in my view was blown way out of proportion. I think the Boost BOD has treated Jon shabbily regarding this incident. My aim here is to correct that. Boost has had a large role in saving C++ from decline into obscurity. David Abrahams and Beman Dawes were the primary promoters at Boost at it's start. I don't think it's too much to say that these two persons saved C++. To this list, I'd like to add the name of Jon Kalb, without whom Boost would likely have wound down with C++11. -- Robert Ramey www.rrsd.com (805)569-3793

4 3

Why do Predef and Config exist?
by Hans Dembinski 27 Dec '22

27 Dec '22

Hi all, since there were concerns that the email list is so quiet, here is some noise. Is someone willing to explain to me why we have Predef and Config? It looks like these two libraries have a strong overlap in scope. Shouldn’t they be merged? Best regards, Hans

10 15

Proposing a Redis client library for inclusion in Boost
by Marcelo Zimbres Silva 22 Dec '22

22 Dec '22

Hi, I would like to propose my Redis client library for inclusion in Boost Github: https://github.com/mzimbres/aedis Homepage: https://mzimbres.github.io/aedis Redis: https://redis.io Aedis implements asynchronous communication with a Redis server using the RESP3 protocol [1] and is built on top of Boost.Asio, which makes it similar to Boost.Beast and Boost.MySql. For more information, please, refer to the project homepage. I am looking for someone who would like to endorse the library and also for a review manager. Thanks, Marcelo [1] https://github.com/redis/redis-specifications/blob/master/protocol/RESP3.md

5 5