March 2022 - Boost - lists.preview.boost.org

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

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

Boost.Text is looking for a (mini-)review manager
by Zach Laine 07 Dec '22

07 Dec '22

I've made all the recommended changes to Boost.Text that came up in the review. Glen, the previous review manager, recommended a mini review of Boost.Text once I'd made those changes. If you'd like to manage the mini-review, please let me know. For everyone, including potential reviewers and review managers, here are the major changes: * All the specific review feedback issues have been addressed. * The string layer is now gone. * The text layer got a major re-work. It is now a set of template-based adaptors (basic_text<>, vs. a text typedef. etc.), which lets everyone get what they want. You can change the underlying storage type (including whatever allocator you prefer), select UTF-8 or UTF-16, and change the normalization form. Glen recommended I drop this layer, but the library is way less useful without this stuff, and these changes address all the concerns raised about the text layer in the review. The updated docs can be found here: https://tzlaine.github.io/text/doc/html/index.html Oh yeah, and I added concept constraints to the whole library when you build in C++20 mode. Zach

17 46

[review][JSON] Review of JSON starts today: Sept 14 - Sept 23
by Pranam Lashkari 09 Aug '22

09 Aug '22

Boost formal review of Vinnie Falco and Krystian Stasiowski's library JSON starts today and will run for 10 days ending on 23 Sept 2020. Both of these authors have already developed a couple of libraries which are accepted in Boost(boost beast and Static String) This library focuses on a common and popular use-case for JSON. It provides a container to hold parsed and serialised JSON types. It provides more flexibility and better benchmark performance than its competitors. JSON highlights the following features in the documentation: - Fast compilation - Require only C++11 - Fast streaming parser and serializer - Easy and safe API with allocator support - Constant-time key lookup for objects - Options to allow non-standard JSON - Compile without Boost, define BOOST_JSON_STANDALONE - Optional header-only, without linking to a library (a point I would like to add in highlight: it has cool Jason logo 😝) To quickly understand and get the flavour of the library take a look at "Quick Look" <http://master.json.cpp.al/json/usage/quick_look.html> You can find the source code to be reviewed here: <https://github.com/CPPAlliance/json/tree/master> You can find the latest documentation here: <http://master.json.cpp.al/> Benchmarks are also given in the document which can be found here: <http://master.json.cpp.al/json/benchmarks.html> Some people have also given the early reviews, the thread can be found here: <https://lists.boost.org/Archives/boost/2020/09/249745.php> Please provide in your review information you think is valuable to understand your choice to ACCEPT or REJECT including JSON as a Boost library. Please be explicit about your decision (ACCEPT or REJECT). Some other questions you might want to consider answering: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With which compiler(s)? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? More information about the Boost Formal Review Process can be found here: <http://www.boost.org/community/reviews.html> Thank you for your effort in the Boost community. -- Thank you, Pranam Lashkari, https://lpranam.github.io/

21 73

[container] Contributing 'stationary_vector' to Boost
by Mehrdad Niknami 13 Jun '22

13 Jun '22

Hi all, Happy new year! New mailing list member here. I've developed an STL-style stationary_vector class that retains elements in-place when growing. Very briefly, it is effectively a piecewise-contiguous vector, with the following advantages over vector: - Appending has O(1) overhead in the *worst* case (e.g., push_back() does not move elements) - Insertion and random-access can be done in parallel, as prior iterators & references remain valid This has a variety of benefits, including better UX (no "hiccups" due to reallocations), and the ability to simplify parallel processing of streaming data. It occurred to me the larger C++ community might find this useful. I was wondering if there would be interest in incorporating it into Boost.Container, and if so, what steps I could take to make that happen? I'm of course happy to discuss the design etc. with anyone who might be interested. Summary: https://github.com/mehrdadn/libvital/blob/master/doc/vital/container/statio… Implementation: https://github.com/mehrdadn/libvital/blob/master/include/vital/container/st… Thank you, Mehrdad

7 19

[release] Boost 1.7.0 beta 1 released
by Marshall Clow 13 Apr '22

13 Apr '22

Boost release 1.77.0 beta 1 is now available at: <https://boostorg.jfrog.io/artifactory/main/beta/1.78.0.beta1/source/> The SHA256 checksums are as follows: 7a3a025451dfa2923129214eef7d16b03c02310a353d02158a549f6caa4284b0 boost_1_78_0_b1.tar.bz2 c491b1dcb916195598aa6581d6708d57fcc750516641c22511c088d572de9c07 boost_1_78_0_b1.tar.gz 35e7a3b0eb412a3933e57c72ba96374eb7d88ff1f89dbec62a16d67ffea2105a boost_1_78_0_b1.7z e6b68feb2f63401c96ca9fe25e939b409189fbe526a6e784e4bd69832c8f09cb boost_1_78_0_b1.zip For details of what's in the release, see <https://www.boost.org/users/history/version_1_78_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

2 1

Proposing a MySQL client library for inclusion in Boost
by Ruben Perez 08 Apr '22

08 Apr '22

Hi all, I would like to propose my MySQL client library for inclusion in Boost. The library features asynchronous communication with MySQL and MariaDB servers, allowing the user to use txt queries and prepared statements. The library is based on Boost.Asio and follows its asynchronous model (in a similar way Boost.Beast does). The library is specific to MySQL and MariaDB systems, and is not intended as a SQL framework or ORM. It fits use cases like HTTP servers (possibly already using Beast), ETL pipelines or any other application that needs to access a MySQL database and wants to benefit from Asio's asynchrony. Please note that the library is a full implementation of MySQL wire protocol and does not use libmysqlclient under the hood. I'm looking for people who officially endorse the library. You can see the code in this GitHub repository <https://github.com/anarthal/mysql>, and the documentation is here <https://anarthal.github.io/mysql/index.html>. Many thanks, Ruben.

4 11

[release] 1.79.0 post-beta merges
by Marshall Clow 06 Apr '22

06 Apr '22

The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>> Reminder: The master branch closes for the release on Wednesday, April 6th. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/> — Marshall P.S Doc changes and test changes do NOT require release manager approval to be merged.

7 12

Should boost have ofind(_if), that returns boost::optional<T&>?
by Ivan Matek 06 Apr '22

06 Apr '22

Hi, I have been thinking for this for a long time so I wanted to get the feedback from others. As you probably know better than me there is a bit of a drama <https://brevzin.github.io/c++/2021/12/13/optional-ref-ptr/>when it comes to std::optional<T&> and from what I see it will not be in C++23 for sure. I believe this gives an opportunity to boost to provide something nice for the users. Now the issues are the following: AFAIK boost only has old ranges and iterator based algorithms, ideally we would just have something like std:: ranges and add the ofind/ofind_if to those, but AFAIK those do not exist. So I think best thing would be to add it to boost::algorithm <https://github.com/boostorg/algorithm/tree/develop/include/boost/algorithm> . There are further questions like, should boost containers like map/unordered_map gain similar functionality, but I think deciding if we want the general algorithm is the first step. Another option I can think of is that those algorithms return something like a 0 or 1 element view(so you could access the optional value with range based for loop). This seems weird to me, so I would prefer boost::optional<T&>. There is s a short example on godbolt <https://godbolt.org/z/W9K3na9Gc>, but don't look at implementation too much, it was just something I hacked quickly, I am mostly interested in in feedback on if functionality would be nice addition to boost. regards, Ivan

5 9

Re: [boost] Proposing a MySQL client library for inclusion in Boost
by Marcelo Zimbres Silva 02 Apr '22

02 Apr '22

Hi Ruben, I have had a look into your library and some questions arise > https://anarthal.github.io/mysql/mysql/ref/boost__mysql__resultset/async_re… > The handler signature for this operation is void(boost::mysql::error_code, std::vector<boost::mysql::row>). > etc. Having a std::vector in the signature of the completion handler is unusual in ASIO. In general large objects should be passed as parameters in the async operation e.g. socket::async_read gets a dynamic_buffer which is a lightweight view to storage. Additionally, there is not support for custom allocators. That wouldn't be a big problem to me if I could reuse the same memory for each request but the interface above prevents me from doing so. > https://anarthal.github.io/mysql/mysql/ref/boost__mysql__connection/async_q… > The handler signature for this operation is void(boost::mysql::error_code, boost::mysql::resultset<Stream>) Hier the completion handler is returning an io object i.e. boost::mysql::resultset, which is also unusual as far as I can see. Does that play nice with executors? I would prefer having the completion handler return config parameters with which I can instantiate a boost::mysql::resultset myself in my desired executor. > https://anarthal.github.io/mysql/mysql/ref/boost__mysql__connection.html I don't see a reason for this class, or at least I fail to see what state does the mysql protocol imposes on you that would justify this class. I would prefer free funcitions much more here, for example, in the same way as beast::http::async_read. > https://anarthal.github.io/mysql/mysql/ref/boost__mysql__value/get_std_opti… > https://anarthal.github.io/mysql/mysql/ref/boost__mysql__value/get_optional… Sounds also unusual to have two member functions for the different versions of optional. Regards, Marcelo

3 7

Boost.URL Proposal max_size
by Alan de Freitas 26 Mar '22

26 Mar '22

Hi! We're deciding on the max size for URLs in our Boost.URL proposal. The spec doesn't suggest a limit but the reasonable trade-off <https://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-…> is: - 2^16 chars: More than all browsers, servers, and search engines support (~2000 chars). More than the HTTP minimum of 8000 octets. - 2^32 chars: "414 Too long request" in practice everywhere. Maybe supports experiments using URLs as a container for something else. Any suggestions? -- Alan Freitas https://github.com/alandefreitas

6 6

Determine interest in a possible library submission
by Keith Hiatt 21 Mar '22

21 Mar '22

Hi All, I was wondering about interest in some derived vector classes which support full vector functionality while adding the capabilities of mathematical operations on the datasets including matrix-based computations. Any thoughts would be appreciated. Thank you, Keith

3 2

Re: [boost] Boost Digest, Vol 6661, Issue 1
by Keith Hiatt 21 Mar '22

21 Mar '22

Hi Vinnie, It is almost complete. Is there a GIT repository where I can upload it? I have not been using a repository for my code and would like to do so. Thank you On Mon, Mar 21, 2022 at 8:00 AM <boost-request(a)lists.boost.org> wrote: > Send Boost mailing list submissions to > boost(a)lists.boost.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.boost.org/mailman/listinfo.cgi/boost > or, via email, send a message with subject or body 'help' to > boost-request(a)lists.boost.org > > You can reach the person managing the list at > boost-owner(a)lists.boost.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Boost digest..." > The boost archives may be found at: http://lists.boost.org/Archives/boost/ > Today's Topics: > > 1. Re: [release] Boost 1.79.0 beta 1 released (Sal Pamukcu) > 2. Re: [release] Boost 1.79.0 beta 1 released (Jeff Trull) > 3. Determine interest in a possible library submission (Keith Hiatt) > 4. Re: Determine interest in a possible library submission > (Vinnie Falco) > > > > ---------- Forwarded message ---------- > From: Sal Pamukcu <salimp2009(a)gmail.com> > To: boost(a)lists.boost.org > Cc: > Bcc: > Date: Sun, 20 Mar 2022 19:40:51 +0300 > Subject: Re: [boost] [release] Boost 1.79.0 beta 1 released > On Fri, Mar 18, 2022 at 1:53 AM Andrey Semashev via Boost < > boost(a)lists.boost.org> wrote: > > > On 3/18/22 00:26, Sal Pamukcu via Boost wrote: > > > On Thu, Mar 17, 2022 at 11:24 PM Andrey Semashev via Boost < > > > boost(a)lists.boost.org> wrote: > > > > > >> On 3/17/22 22:31, Sal Pamukcu via Boost wrote: > > >>> - Compiled on Win 11 MSVC 2002 x64 toolchain with c++20 using > > >>> b2 cxxstd=20 --build-type=complete stage > > >>> > > >>> failed 5 target ; (mostly related to python) > > >>> The full built message are on gist ; > > >>> boost179b1_MSVC (github.com) > > >>> <https://gist.github.com/salimp2009/074cf168b4dd1231aa92fcc3845e2df7 > > > > >>> > > >>> I will do another build on windows with gcc-11.2 with MSys; > > >>> > > >>> ``` > > >>> ...failed updating 5 targets... > > >>> ...skipped 9 targets... > > >>> ...updated 8376 targets... > > >>> ``` > > >>> > > >>> Failures are like this ; > > >>> `...failed msvc.link.dll > > >>> > > >> > > > bin.v2\libs\python\build\msvc-14.3\debug\address-model-32\cxxstd-20-iso\python-3.10\threading-multi\boost_python310-vc143-mt-gd-x32-1_79.dll > > >>> > > >> > > > bin.v2\libs\python\build\msvc-14.3\debug\address-model-32\cxxstd-20-iso\python-3.10\threading-multi\boost_python310-vc143-mt-gd-x32-1_79.lib > > >>> > > >> > > > bin.v2\libs\python\build\msvc-14.3\debug\address-model-32\cxxstd-20-iso\python-3.10\threading-multi\boost_python310-vc143-mt-gd-x32-1_79.pdb...` > > >> > > >> Looks like the problem is that you're building 32-bit Boost.Python and > > >> linking with 64-bit Python libraries. I'm not sure if Boost.Python is > > >> supposed to find the correct libraries or this is just a user > > >> configuration error. > > > > > > Do you mean my configuration mistake; > > > i installed python 3.10 64 bit > > > and checked from MSVC VS 2022 64 bit command line using this ; > > > It looks like my Python is 64 bit; > > > > > > C:\Program Files\Microsoft Visual Studio\2022\Community> > > > C:\Program Files\Microsoft Visual Studio\2022\Community>python > > > Python 3.10.0 (tags/v3.10.0:b494f59, Oct 4 2021, 19:00:18) [MSC v.1929 > > 64 > > > bit (AMD64)] on win32 > > > Type "help", "copyright", "credits" or "license" for more information. > > >>>> import struct > > >>>> version = struct.calcsize("P")*8 > > >>>> print(version) > > > 64 > > >>>> > > > > > > is there a way to configure when building with b2 > > > I used this ; b2 cxxstd=20 --build-type=complete stage > > > > By default both 32 and 64-bit Boost binaries are built. To build only > > 64-bit binaries you can add address-model=64 to the b2 command line. If > > you want to build 32-bit libraries, use address-model=32 and also make > > sure 32-bit Python libraries are found by the build process. > > > > _______________________________________________ > > Unsubscribe & other changes: > > http://lists.boost.org/mailman/listinfo.cgi/boost > > > > I did another build on Windows 11 ; this time using gcc-11.2 (via MSys2 > MinGW), c++20 > I did 2 runs one on command line and one on x64 Native Tool MSCV 2022 > Also used address-model=64 to avoid Python 32-bit > No errors but compiled way less files this time ; typically it was around > ~8000+ > this time "...updated 3693 targets.." > command line i used ; > b2 cxxstd=20 address-model=64 toolset=gcc --build-type=complete stage > > as usual got warning for auto_ptr and this one ; > > C:/msys64/mingw64/include/c++/11.2.0/ext/new_allocator.h:145:26: warning: > 'void operator delete(void*, std::size_t)' called on unallocated object > 'boost::wave::util::SimpleStringStorage<char, std::allocator<char> > >::emptyString_' [-Wfree-nonheap-object] > 145 | ::operator delete(__p > | ~~~~~~~~~~~~~~~~~^~~~ > 146 | #if __cpp_sized_deallocation > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > 147 | , __t * sizeof(_Tp) > | ~~~~~~~~~~~~~~~~~~~ > 148 | #endif > | ~~~~~~ > 149 | ); > > If needed I can put the whole build outputs on gist. > > Only one question is it normal to use address-model=64 or should this be > detected thru b2 or CMake and if it causes any other needed > libraries skipped because there was quite a bit of difference in the > updated amount > > Salim Pamukcu > > > > > ---------- Forwarded message ---------- > From: Jeff Trull <linmodemstudent(a)gmail.com> > To: Boost Developers List <boost(a)lists.boost.org> > Cc: > Bcc: > Date: Sun, 20 Mar 2022 10:21:18 -0700 > Subject: Re: [boost] [release] Boost 1.79.0 beta 1 released > On Sun, Mar 20, 2022 at 9:41 AM Sal Pamukcu via Boost < > boost(a)lists.boost.org> > wrote: > > > On Fri, Mar 18, 2022 at 1:53 AM Andrey Semashev via Boost < > > boost(a)lists.boost.org> wrote: > > > > > On 3/18/22 00:26, Sal Pamukcu via Boost wrote: > > > > On Thu, Mar 17, 2022 at 11:24 PM Andrey Semashev via Boost < > > > > boost(a)lists.boost.org> wrote: > > > > > > > >> On 3/17/22 22:31, Sal Pamukcu via Boost wrote: > > > >>> - Compiled on Win 11 MSVC 2002 x64 toolchain with c++20 using > > > >>> b2 cxxstd=20 --build-type=complete stage > > > >>> > > > >>> failed 5 target ; (mostly related to python) > > > >>> The full built message are on gist ; > > > >>> boost179b1_MSVC (github.com) > > > >>> < > https://gist.github.com/salimp2009/074cf168b4dd1231aa92fcc3845e2df7 > > > > > > >>> > > > >>> I will do another build on windows with gcc-11.2 with MSys; > > > >>> > > > >>> ``` > > > >>> ...failed updating 5 targets... > > > >>> ...skipped 9 targets... > > > >>> ...updated 8376 targets... > > > >>> ``` > > > >>> > > > >>> Failures are like this ; > > > >>> `...failed msvc.link.dll > > > >>> > > > >> > > > > > > bin.v2\libs\python\build\msvc-14.3\debug\address-model-32\cxxstd-20-iso\python-3.10\threading-multi\boost_python310-vc143-mt-gd-x32-1_79.dll > > > >>> > > > >> > > > > > > bin.v2\libs\python\build\msvc-14.3\debug\address-model-32\cxxstd-20-iso\python-3.10\threading-multi\boost_python310-vc143-mt-gd-x32-1_79.lib > > > >>> > > > >> > > > > > > bin.v2\libs\python\build\msvc-14.3\debug\address-model-32\cxxstd-20-iso\python-3.10\threading-multi\boost_python310-vc143-mt-gd-x32-1_79.pdb...` > > > >> > > > >> Looks like the problem is that you're building 32-bit Boost.Python > and > > > >> linking with 64-bit Python libraries. I'm not sure if Boost.Python > is > > > >> supposed to find the correct libraries or this is just a user > > > >> configuration error. > > > > > > > > Do you mean my configuration mistake; > > > > i installed python 3.10 64 bit > > > > and checked from MSVC VS 2022 64 bit command line using this ; > > > > It looks like my Python is 64 bit; > > > > > > > > C:\Program Files\Microsoft Visual Studio\2022\Community> > > > > C:\Program Files\Microsoft Visual Studio\2022\Community>python > > > > Python 3.10.0 (tags/v3.10.0:b494f59, Oct 4 2021, 19:00:18) [MSC > v.1929 > > > 64 > > > > bit (AMD64)] on win32 > > > > Type "help", "copyright", "credits" or "license" for more > information. > > > >>>> import struct > > > >>>> version = struct.calcsize("P")*8 > > > >>>> print(version) > > > > 64 > > > >>>> > > > > > > > > is there a way to configure when building with b2 > > > > I used this ; b2 cxxstd=20 --build-type=complete stage > > > > > > By default both 32 and 64-bit Boost binaries are built. To build only > > > 64-bit binaries you can add address-model=64 to the b2 command line. If > > > you want to build 32-bit libraries, use address-model=32 and also make > > > sure 32-bit Python libraries are found by the build process. > > > > > > _______________________________________________ > > > Unsubscribe & other changes: > > > http://lists.boost.org/mailman/listinfo.cgi/boost > > > > > > > I did another build on Windows 11 ; this time using gcc-11.2 (via MSys2 > > MinGW), c++20 > > I did 2 runs one on command line and one on x64 Native Tool MSCV 2022 > > Also used address-model=64 to avoid Python 32-bit > > No errors but compiled way less files this time ; typically it was around > > ~8000+ > > this time "...updated 3693 targets.." > > command line i used ; > > b2 cxxstd=20 address-model=64 toolset=gcc --build-type=complete stage > > > > as usual got warning for auto_ptr and this one ; > > > > C:/msys64/mingw64/include/c++/11.2.0/ext/new_allocator.h:145:26: warning: > > 'void operator delete(void*, std::size_t)' called on unallocated object > > 'boost::wave::util::SimpleStringStorage<char, std::allocator<char> > > >::emptyString_' [-Wfree-nonheap-object] > > 145 | ::operator delete(__p > > | ~~~~~~~~~~~~~~~~~^~~~ > > 146 | #if __cpp_sized_deallocation > > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > 147 | , __t * sizeof(_Tp) > > | ~~~~~~~~~~~~~~~~~~~ > > 148 | #endif > > | ~~~~~~ > > 149 | ); > > > > If needed I can put the whole build outputs on gist. > > > This looks like the same issue as > https://github.com/boostorg/wave/issues/159. > I think it's a new analysis in gcc 11 that we haven't seen before (and > therefore not > a regression). > > > > > Only one question is it normal to use address-model=64 or should this be > > detected thru b2 or CMake and if it causes any other needed > > libraries skipped because there was quite a bit of difference in the > > updated amount > > > > Salim Pamukcu > > > > _______________________________________________ > > Unsubscribe & other changes: > > http://lists.boost.org/mailman/listinfo.cgi/boost > > > > > > > ---------- Forwarded message ---------- > From: Keith Hiatt <keith.x.hiatt(a)gmail.com> > To: boost(a)lists.boost.org > Cc: > Bcc: > Date: Sun, 20 Mar 2022 21:55:50 -0400 > Subject: [boost] Determine interest in a possible library submission > Hi All, > > I was wondering about interest in some derived vector classes which support > full vector functionality while adding the capabilities of mathematical > operations on the datasets including matrix-based computations. > > Any thoughts would be appreciated. > > Thank you, > Keith > > > > > ---------- Forwarded message ---------- > From: Vinnie Falco <vinnie.falco(a)gmail.com> > To: "boost(a)lists.boost.org List" <boost(a)lists.boost.org> > Cc: > Bcc: > Date: Sun, 20 Mar 2022 22:48:54 -0700 > Subject: Re: [boost] Determine interest in a possible library submission > On Sun, Mar 20, 2022 at 10:03 PM Keith Hiatt via Boost > <boost(a)lists.boost.org> wrote: > > I was wondering about interest in some derived vector classes which > support > > full vector functionality while adding the capabilities of mathematical > > operations on the datasets including matrix-based computations. > > If this is already written, could you please share a link? > > Thanks > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

1 0

Boost 1.78.0 build issue
by Daggumati, Rajesh 21 Mar '22

21 Mar '22

Hi Team, I have built 1.76.0 sucessfully in my visual studio 2019 but when I try to build boost 1.78.0, I am facing some linker issue like below. Please help me to fix it. Severity Code Description Project File Line Suppression State Error LNK1104 cannot open file 'libboost_filesystem-vc142-mt-gd-x64-1_78.lib' checksum-writer-xml C:\Projects\Abba\src-cpp\src\apps\checksum-writer-xml\LINK 1 Error LNK1104 cannot open file 'libboost_filesystem-vc142-mt-gd-x64-1_78.lib' IPLUtilityTest C:\Projects\Abba\src-cpp\src\modules\IPLUtilityTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' FoundationQtTest C:\Projects\Abba\src-cpp\src\modules\FoundationQtTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' FoundationTest C:\Projects\Abba\src-cpp\src\modules\FoundationTest\LINK 1 Error LNK1104 cannot open file 'libboost_program_options-vc142-mt-gd-x64-1_78.lib' console-test-harness C:\Projects\Abba\src-cpp\src\apps\console-test-harness\LINK 1 Error LNK1104 cannot open file 'libboost_filesystem-vc142-mt-gd-x64-1_78.lib' InstrumentTest C:\Projects\Abba\src-cpp\src\modules\InstrumentTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' InstrumentQtTest C:\Projects\Abba\src-cpp\src\modules\InstrumentQtTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' widget-test-harness C:\Projects\Abba\src-cpp\src\apps\widget-test-harness\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' cytiva-aktaflux C:\Projects\Abba\src-cpp\src\apps\cytiva-aktaflux\LINK 1 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.

1 0

Boost 1.78.0 build issue
by Daggumati, Rajesh 21 Mar '22

21 Mar '22

Hi Team, I have built 1.76.0 sucessfully in my visual studio 2019 but when I try to build boost 1.78.0, I am facing some linker issue like below. Please help me to fix it. Severity Code Description Project File Line Suppression State Error LNK1104 cannot open file 'libboost_filesystem-vc142-mt-gd-x64-1_78.lib' checksum-writer-xml C:\Projects\Abba\src-cpp\src\apps\checksum-writer-xml\LINK 1 Error LNK1104 cannot open file 'libboost_filesystem-vc142-mt-gd-x64-1_78.lib' IPLUtilityTest C:\Projects\Abba\src-cpp\src\modules\IPLUtilityTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' FoundationQtTest C:\Projects\Abba\src-cpp\src\modules\FoundationQtTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' FoundationTest C:\Projects\Abba\src-cpp\src\modules\FoundationTest\LINK 1 Error LNK1104 cannot open file 'libboost_program_options-vc142-mt-gd-x64-1_78.lib' console-test-harness C:\Projects\Abba\src-cpp\src\apps\console-test-harness\LINK 1 Error LNK1104 cannot open file 'libboost_filesystem-vc142-mt-gd-x64-1_78.lib' InstrumentTest C:\Projects\Abba\src-cpp\src\modules\InstrumentTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' InstrumentQtTest C:\Projects\Abba\src-cpp\src\modules\InstrumentQtTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' widget-test-harness C:\Projects\Abba\src-cpp\src\apps\widget-test-harness\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' cytiva-aktaflux C:\Projects\Abba\src-cpp\src\apps\cytiva-aktaflux\LINK 1 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.

1 0

[release] Boost 1.79.0 beta 1 released
by Marshall Clow 20 Mar '22

20 Mar '22

Boost release 1.79.0 beta 1 is now available at: <https://boostorg.jfrog.io/artifactory/main/beta/1.79.0.beta1/source/> The SHA256 checksums are as follows: 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1.tar.gz 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1.7z 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1.zip For details of what's in the release, see <https://www.boost.org/users/history/version_1_79_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

4 6

numeric_cast should work with enum's
by Frederick Virchanza Gotham 16 Mar '22

16 Mar '22

(Sometimes Gmail takes out white space so I'm hoping this post is indented properly.) I think that "numeric_cast" should be able to cast to and from enum types, so that it can be used as follows: #include <cstdint> #include <iostream> using std::cout; using std::endl; enum class Toad : std::uint8_t { Purple, Orange = 0x7f }; enum class Frog { Blue, Yellow, Pink = 0xFFFFu }; int main(void) { try { numeric_cast<Toad>( Frog::Pink ); } catch(std::exception const &e) { cout << e.what() << endl; } std::uint32_t my_32_bit_var = 0xffffffffU; try { numeric_cast<std::uint16_t>(my_32_bit_var); } catch(std::exception const &e) { cout << e.what() << endl; } try { numeric_cast<std::uint8_t>( Frog::Pink ); } catch(std::exception const &e) { cout << e.what() << endl; } try { numeric_cast<Toad>(0x1FFu); } catch(std::exception const &e) { cout << e.what() << endl; } } In order to achieve this behaviour, I've created my own "numeric_cast" in the global namespace as follows: #include <type_traits> // is_enum, underlying_type #include <boost/numeric/conversion/cast.hpp> // numeric_cast template<bool T_is_an_enum, typename T> struct numeric_cast_helper { typedef T type; }; template<typename T> struct numeric_cast_helper<true, T> { typedef typename std::underlying_type<T>::type type; }; template<typename A, typename B> A numeric_cast(B const b) // This function takes its argument by value, and also returns by value -- which is fine for arithmetic types { return static_cast<A>( boost::numeric_cast<typename numeric_cast_helper<std::is_enum<A>::value, A>::type> ( static_cast<typename numeric_cast_helper<std::is_enum<B>::value, B>::type>(b) ) ); }

1 0

Fwd: Boost Digest, Vol 6656, Issue 1
by Sal Pamukcu 11 Mar '22

11 Mar '22

---------- Forwarded message --------- From: <boost-request(a)lists.boost.org> Date: Fri, Mar 11, 2022 at 3:00 PM Subject: Boost Digest, Vol 6656, Issue 1 To: <boost(a)lists.boost.org> Send Boost mailing list submissions to boost(a)lists.boost.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.boost.org/mailman/listinfo.cgi/boost or, via email, send a message with subject or body 'help' to boost-request(a)lists.boost.org You can reach the person managing the list at boost-owner(a)lists.boost.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Boost digest..." The boost archives may be found at: http://lists.boost.org/Archives/boost/ Today's Topics: 1. Re: [Graph] Attempt to resolve open issue (Anne van de Graaf) 2. Master branch now closed for 1.79.0 beta release (Marshall Clow) 3. [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Marshall Clow) 4. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Marshall Clow) 5. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Andrey Semashev) 6. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Marshall Clow) 7. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Andrey Semashev) 8. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Tom Kent) 9. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Matt Borland) 10. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Andrey Semashev) ---------- Forwarded message ---------- From: Anne van de Graaf <A.vandeGraaf(a)dianafea.com> To: Jeremy Murphy <jeremy.william.murphy(a)gmail.com> Cc: "boost(a)lists.boost.org" <boost(a)lists.boost.org>, John Maddock < jz.maddock(a)googlemail.com> Bcc: Date: Thu, 10 Mar 2022 13:17:37 +0000 Subject: Re: [boost] [Graph] Attempt to resolve open issue > This is fixed on the develop branch, btw, have you verified that it works as expected now? Apologies for my late reply. Yes, I have verified that the fix on the develop branch works as expected. Thank you very much for the work that you have done. Best regards, Anne On Fri, 10 Dec 2021 at 18:56, Anne van de Graaf <A.vandeGraaf(a)dianafea.com <mailto:A.vandeGraaf@dianafea.com>> wrote: > Hi Anne, > which issue or pull request # is it? Hi Jeremy, It is issue # 268: https://github.com/boostorg/graph/issues/268 Best regards, Anne > Jeremy On Sun, 5 Dec 2021 at 02:20, Anne van de Graaf via Boost < boost(a)lists.boost.org<mailto:boost@lists.boost.org>> wrote: > Hello all, > > I am trying to get an open issue in Boost.Graph resolved. Since I haven't received any response at the corresponding GitHub page nor from the Boost Users mailing list (where I posted the below message last Monday), I am reaching out to you. My aim is to get in touch with the maintainer(s) of Boost.Graph in order to discuss what is the preferred/most efficient way to fix the issue. Since this is my first post to this mailing list, please accept my apologies if you feel this is not the right way to get in touch with the maintainers. In that case, I would appreciate it very much if you could kindly explain what I should have done instead. Please find below a copy of my message that I sent last Monday to the Boost Users mailing list. Thank you very much for your attention and any replies. > Unfortunately, Graph has no current maintainer. I have done some > maintenance on that library in the past, and I know Jeremy Murphy will > be trying to do some this next week, so hopefully one of us can get that > one fixed! Thanks a lot for your reply, John. I didn't know that Boost.Graph doesn't have a current maintainer. It would be great if you or Jeremy could do some maintenance on it. Feel free to contact me if I can help you in any way to get things done. We could then discuss in what way I can contribute. Thanks. Kind regards, Anne > Best, John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost ---------- Forwarded message ---------- From: Marshall Clow <mclow.lists(a)gmail.com> To: Boost Developers List <boost(a)lists.boost.org> Cc: Bcc: Date: Thu, 10 Mar 2022 06:31:06 -0800 Subject: [boost] Master branch now closed for 1.79.0 beta release Please do not make any commits to the master branch. — Marshall ---------- Forwarded message ---------- From: Marshall Clow <mclow.lists(a)gmail.com> To: Boost Developers List <boost(a)lists.boost.org> Cc: Bcc: Date: Thu, 10 Mar 2022 07:27:19 -0800 Subject: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> The SHA256 checksums are as follows: 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_rc1.7z As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers It fails on Window 11 using GCC-11.2 command line ; b2 cxxstd=20 toolset=gcc --build-type=complete stage here is the error message ; FailBoost1.79.0 Beta 1 Release Candidate 1 (github.com) <https://gist.github.com/salimp2009/854b3c74295b2487c4585be35f8bfbd0> Salim (a new bee in devel :) ---------- Forwarded message ---------- From: Marshall Clow <mclow.lists(a)gmail.com> To: Boost Developers List <boost(a)lists.boost.org> Cc: Bcc: Date: Thu, 10 Mar 2022 08:03:12 -0800 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On Mar 10, 2022, at 7:27 AM, Marshall Clow <mclow.lists(a)gmail.com> wrote: > > are now available at: > <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> > > The SHA256 checksums are as follows: > > 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 > 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz > 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip > 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_rc1.7z > > As always, the release managers would appreciate it if you download the > candidate of your choice and give building it a try. Please report both > success and failure, and anything else that is noteworthy. I have successfully built the libraries: * On Mac OS 10.15, using Apple clang version 11.0.3, and and c++03/11/14/17/2a — Marshall ---------- Forwarded message ---------- From: Andrey Semashev <andrey.semashev(a)gmail.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Thu, 10 Mar 2022 20:17:42 +0300 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On 3/10/22 18:27, Marshall Clow via Boost wrote: > are now available at: > <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> > > The SHA256 checksums are as follows: > > 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 > 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz > 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip > 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_rc1.7z > > As always, the release managers would appreciate it if you download the > candidate of your choice and give building it a try. Please report both > success and failure, and anything else that is noteworthy. I'm trying to download the source package now, and the download speed is terrible, ~30-60 KB/s. Is this expected? ---------- Forwarded message ---------- From: Marshall Clow <mclow.lists(a)gmail.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Thu, 10 Mar 2022 09:53:08 -0800 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On Mar 10, 2022, at 9:17 AM, Andrey Semashev via Boost < boost(a)lists.boost.org> wrote: > > On 3/10/22 18:27, Marshall Clow via Boost wrote: >> are now available at: >> <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> >> >> The SHA256 checksums are as follows: >> >> 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 >> 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz >> 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip >> 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_rc1.7z >> >> As always, the release managers would appreciate it if you download the >> candidate of your choice and give building it a try. Please report both >> success and failure, and anything else that is noteworthy. > > I'm trying to download the source package now, and the download speed is > terrible, ~30-60 KB/s. Is this expected? That’s not what I’m seeing. I’m getting > 1 MB/sec — Marshall ---------- Forwarded message ---------- From: Andrey Semashev <andrey.semashev(a)gmail.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Thu, 10 Mar 2022 21:25:53 +0300 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On 3/10/22 20:53, Marshall Clow via Boost wrote: > On Mar 10, 2022, at 9:17 AM, Andrey Semashev via Boost < boost(a)lists.boost.org> wrote: >> >> On 3/10/22 18:27, Marshall Clow via Boost wrote: >>> are now available at: >>> <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> >>> >>> The SHA256 checksums are as follows: >>> >>> 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 >>> 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz >>> 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip >>> 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_rc1.7z >>> >>> As always, the release managers would appreciate it if you download the >>> candidate of your choice and give building it a try. Please report both >>> success and failure, and anything else that is noteworthy. >> >> I'm trying to download the source package now, and the download speed is >> terrible, ~30-60 KB/s. Is this expected? > > That’s not what I’m seeing. > I’m getting > 1 MB/sec Possibly, some regional restrictions on JFrog side? I'm not seeing bandwidth issues on other sites, including GitHub, which I assume is US based. BTW, building with gcc 11.2 in C++17 mode on Kubuntu 21.10 succeeds. There are quite a few warnings about auto_ptr being deprecated, and also some suspicious warnings about freeing non-heap-allocated objects in Boost.Wave: https://github.com/boostorg/wave/issues/159 ---------- Forwarded message ---------- From: Tom Kent <lists(a)teeks99.com> To: Boost Developers List <boost(a)lists.boost.org> Cc: Bcc: Date: Thu, 10 Mar 2022 15:33:30 -0600 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On Thu, Mar 10, 2022 at 9:27 AM Marshall Clow via Boost < boost(a)lists.boost.org> wrote: > are now available at: > <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < > https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> > > The SHA256 checksums are as follows: > > 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf > boost_1_79_0_b1_rc1.tar.bz2 > 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 > boost_1_79_0_b1_rc1.tar.gz > 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b > boost_1_79_0_b1_rc1.zip > 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 > boost_1_79_0_b1_rc1.7z > > As always, the release managers would appreciate it if you download the > candidate of your choice and give building it a try. Please report both > success and failure, and anything else that is noteworthy. > > -- The Release Managers > Looks good on Windows/Visual Studio. toolset arch compile Link Execute msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 X X X msvc-14.1 32 X X X msvc-14.1 64 X X X msvc-14.2 32 X X X msvc-14.2 64 X X X msvc-14.3 32 X X X msvc-14.3 64 X X X Compile means that the b2 command completed without errors Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors. Full build logs can be found here: https://gist.github.com/teeks99/acf919a716deeb001acaa2b4f12cb757 Tom ---------- Forwarded message ---------- From: Matt Borland <matt(a)mattborland.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Fri, 11 Mar 2022 10:57:15 +0000 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available > 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 > > _______________________________________________ Boost.Filesystem fails to build using Apple Clang 13 with C++11/14/17/20 on M1 Pro Architecture. An issue has been opened here ( https://github.com/boostorg/filesystem/issues/231) Matt ---------- Forwarded message ---------- From: Andrey Semashev <andrey.semashev(a)gmail.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Fri, 11 Mar 2022 14:09:22 +0300 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On 3/11/22 13:57, Matt Borland via Boost wrote: >> 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 >> >> _______________________________________________ > > Boost.Filesystem fails to build using Apple Clang 13 with C++11/14/17/20 on M1 Pro Architecture. An issue has been opened here ( https://github.com/boostorg/filesystem/issues/231) As replied in the issue, your build is picking up headers from a different Boost version in /usr/local/include. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost -- Salim Pamukcu

1 0

[release] Boost 1.79.0 Beta 1 Release Candidate 1 is available
by Marshall Clow 11 Mar '22

11 Mar '22

are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> The SHA256 checksums are as follows: 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_rc1.7z As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers

4 8

Master branch now closed for 1.79.0 beta release
by Marshall Clow 10 Mar '22

10 Mar '22

Please do not make any commits to the master branch. — Marshall

1 0

[Graph] Attempt to resolve open issue
by Anne van de Graaf 10 Mar '22

10 Mar '22

Hello all, I am trying to get an open issue in Boost.Graph resolved. Since I haven't received any response at the corresponding GitHub page nor from the Boost Users mailing list (where I posted the below message last Monday), I am reaching out to you. My aim is to get in touch with the maintainer(s) of Boost.Graph in order to discuss what is the preferred/most efficient way to fix the issue. Since this is my first post to this mailing list, please accept my apologies if you feel this is not the right way to get in touch with the maintainers. In that case, I would appreciate it very much if you could kindly explain what I should have done instead. Please find below a copy of my message that I sent last Monday to the Boost Users mailing list. Thank you very much for your attention and any replies. Original message: When I remove a vertex from a graph, I occasionally experience a crash (on a system running Red Hat Enterprise Linux 8.5). I have been able to replicate the behavior with the following test program: #include <vector> #include <boost/graph/adjacency_list.hpp> int main() { using MyGraph = boost::adjacency_list<boost::setS, boost::vecS, boost::undirectedS>; using MyVertexDescriptor = boost::graph_traits<MyGraph>::vertex_descriptor; using MyVertexDescriptorVec = std::vector<MyVertexDescriptor>; MyGraph g; MyVertexDescriptorVec vertices{ boost::add_vertex( g ), boost::add_vertex( g ), boost::add_vertex( g ) }; boost::add_edge( vertices[0], vertices[1], g ); boost::add_edge( vertices[1], vertices[2], g ); boost::clear_vertex( vertices[0], g ); boost::remove_vertex( vertices[0], g ); return 0; } Also on a Windows platform, I observe similar behavior. When I build the above code with Microsoft Visual Studio 2019 (MSVC 14.27.29110) and run it with a debugger, a debug assertion is triggered ("cannot increment value-initialized map/set iterator"). In both cases (on Linux and Windows platforms), the debugger reveals that the problem is at line 2071 of boost/graph/detail/adjacency_list.hpp. For clarity, I have copied the involved template function below: template < class EdgeList, class vertex_descriptor > inline void reindex_edge_list( EdgeList& el, vertex_descriptor u, boost::disallow_parallel_edge_tag) { for (typename EdgeList::iterator ei = el.begin(); ei != el.end(); ++ei) // line 2071: increment operator fails { if (ei->get_target() > u) { typename EdgeList::value_type ce = *ei; el.erase(ce); --ce.get_target(); el.insert(ce); } } } While I was searching for a proper place to post my question, I found the following issue at GitHub (which was opened on July 1 of this year): https://github.com/boostorg/graph/issues/268. This appears to be the exact same issue. So last week, I added a comment saying that I am facing the exact same problem. Unfortunately, so far no one has responded yet. To me, it seems that the problem is well-understood. Also, some have proposed a bug fix to resolve the issue (including a pull request). Nevertheless, no progress has been made over the past months. So I was just wondering what is the best way to proceed if we want to fix the issue in Boost itself? Is there anything that I can do (apart from starting this thread) to help in resolving the issue? Any feedback is greatly appreciated. Kind regards, Anne van de Graaf

3 6

Windows Build Issue for Boost Wave
by Tom Kent 09 Mar '22

09 Mar '22

In preparation for the lockdown today, I did a dry run of the windows build based on the latest snapshot. During this build I encountered errors with wave on the msvc-12.0 compiler (both 32 & 64 bit). Roughly the following is repeated several times during the build: compile-c-c++ D:\RB\bin.v2\boost\bin.v2\libs\wave\build\msvc-12.0\debug\address-model-32\threading-multi\token_ids.obj token_ids.cpp D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(335) : error C2146: syntax error : missing ';' before identifier 'token_id' D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(335) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(341) : error C2146: syntax error : missing ';' before identifier 'token_id' D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(341) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(341) : error C2086: 'int boost::wave::constexpr' : redefinition D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(335) : see declaration of 'boost::wave::constexpr' D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(347) : error C2144: syntax error : 'bool' should be preceded by ';' D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(347) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(347) : error C2086: 'int boost::wave::constexpr' : redefinition D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(335) : see declaration of 'boost::wave::constexpr' call "D:\RB\bin.v2\boost\bin.v2\standalone\msvc\msvc-12.0\address-model-32\architecture-x86\msvc-setup.bat" x86 >nul cl /Zm800 -nologo "libs\wave\src\token_ids.cpp" -c -Fo"D:\RB\bin.v2\boost\bin.v2\libs\wave\build\msvc-12.0\debug\address-model-32\threading-multi\token_ids.obj" -TP /wd4675 /EHs /GR /Z7 /Od /Ob0 /W3 /MDd /Zc:forScope /Zc:wchar_t /Zc:inline -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -D_CRT_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_DEPRECATE "-I." ...failed compile-c-c++ D:\RB\bin.v2\boost\bin.v2\libs\wave\build\msvc-12.0\debug\address-model-32\threading-multi\token_ids.obj... Hope this helps, if not fixed it will be blocking the beta rc when it gets rolled. Tom

1 0

Boost 1.79.0 closed for breaking changes and new libraries today
by Glen Fernandes 02 Mar '22

02 Mar '22

We are closed for new libraries and breaking changes today. We will close for all major changes this Friday (2022-03-04). And will close for the beta the following Wednesday (2022-03-09). The Release Managers

1 0