- Boost - lists.preview.boost.org

So.... what are we going to do about modules?
by John Maddock 06 Apr '22

06 Apr '22

The title says it all really, but in more detail: 1) Is there any existing best practice we should follow yet? 2) Can we share code content effectively between headers and modules? And by modules I mean "proper" ones: we should be able to write "import boost.whatever;" rather than importing a header. 3) What directory structure should we all be using for module definition files? 4) Do we have Boost.Build support yet? 5) What file extensions should we be using? 6) I presume we would all use the boost.libraryname and boost.libraryname.sub_feature naming convention with boost.libraryname pulling in the whole library? 7) Does anyone have a handle on the current state of std library modularization? 8) Is there demand for this? And no doubt lots of other things I haven't thought of. Curiously yours, John.

11 27

Permission to merge bug fix to Outcome
by Niall Douglas 06 Apr '22

06 Apr '22

Issue being fixed is https://github.com/ned14/outcome/issues/259 where enabling of move assignment was not calculated correctly. (To be specific, if both T and E implement move assignment and default construction, but not move nor copy construction, we did not enable move assignment before and with this fix now we do) Code fixing it is at https://github.com/ned14/outcome/pull/260 Fix passes on develop branch at https://www.boost.org/development/tests/develop/developer/outcome.html Niall

2 4

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

regarding performance of boost::recursive_mutex::scoped_lock
by Daggumati, Rajesh 04 Apr '22

04 Apr '22

Hi Team, boost::recursive_mutex::scoped_lock behavior is same in linux and windows? I am getting some delay in my project which is in windows but same project in linux is not getting delayed. 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.

2 1

[release][multi_index] permission to merge to master
by Joaquin M López Muñoz 03 Apr '22

03 Apr '22

Hi, the following PR is absolutely trivial https://github.com/boostorg/multi_index/pull/57 but seems like it's important to Bitcoin guys in connection with an effort to prune internal Boost dependencies they're carrying out. Can I merge to master or should I wait till Boost 1.80? Thank you, Joaquín M López Muñoz

2 2

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