- Boost-users - lists.preview.boost.org

[PFR] names_as_array doesn't work for structs with array fields
by Chinmay Dalal 23 Sep '24

23 Sep '24

Hi, `boost::pfr::names_as_array<T>()` does not compile if `T` has an array member. Someone commented a fix on a similar issue: https://github.com/boostorg/pfr/issues/170 What would be the appropriate place to ask for including this fix? Background: I'm trying to print structs as CSV. I came up with this: https://paste.sr.ht/~p00f/667e013c23c991ddec91e9cdaa00bd3c11cb2ceb But as soon as I include an array member: https://paste.sr.ht/~p00f/aa08531cd100f8b94c49ead2c541ff96f55b362e it does not compile: https://paste.sr.ht/~p00f/636c1e3ab4f5ba86aa865f70f32337b3d2872047 Thanks, Chinmay

1 0

Boost.Asio UDP sockets guarantee for ordering
by Kalesis, Ioannis 18 Sep '24

18 Sep '24

Hello, I am using boost.asio for udp sockets to broadcast multicast traffic. For that, I am using async_send methods. I am aware that there is no guarantee for the order of the completion handlers for the async_send calls, and for that reason I have implemented a queueing mechanism, where the coroutine waits for the current async_send to complete before moving forward to the next call. However, given the low latency requirement of the application, I believe that the following approach may be more optimal: * The async_send operation would happen immediately one after another (not concurrently) without waiting for the previous ones to complete. * The queueing mechanism would be used but only for the post processing work completion handlers. The above will provide both better latency (by sending the packets sooner instead of having to enqeue/spawn_co/dequeue) and still maintain the strict ordering requirement of the post processing work. However, one concern that I have with this approach is with the "multiple" async_send calls being made one after the other. After searching on this topic, I arrived at the conclusion that this is "safe" given that they are not composed operations so there is no risk that the data will be interleaved between packets. The point that I need help understanding is whether there is a guarantee on the order of the packets being enqueued to kernels network stack. For the following example: ``` udp_socket.async_send(packet1,...); upd_socket.async_send(packet2,...); ``` Is there any possible way for "packet2" to be enqueued 1st in the kernel network stack? Similarly, Is it possible for it to be sent by the OS 1st? I acknowledge that even if everything went perfect on the machine, packets could still be received out-of-order to the clients and that is acceptable, however I would like at least to not have the application contribute to this as part of a software issue. The application has multiple threads that run the same io_context with strands in place to have thread-safety. My machine is a redhat 9, gcc 11.4 Thank you in advance for your time and cooperation. Best regards

4 4

Re: [Boost-users] Boost-users Digest, Vol 5734, Issue 1
by Oran Johnson 09 Sep '24

09 Sep '24

Any ideas as to how to correct the following? johnson@fedora:~/opensource$ svn co https://svn.boost.org/svn/boost/sandbox sandbox svn: E170013: Unable to connect to a repository at URL 'https://svn.boost.org/svn/boost/sandbox' svn: E000111: Error running context: Connection refused ________________________________ From: Boost-users <boost-users-bounces(a)lists.boost.org> on behalf of boost-users-request(a)lists.boost.org <boost-users-request(a)lists.boost.org> Sent: Tuesday, August 27, 2024 8:00 AM To: boost-users(a)lists.boost.org <boost-users(a)lists.boost.org> Subject: Boost-users Digest, Vol 5734, Issue 1 Send Boost-users mailing list submissions to boost-users(a)lists.boost.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.boost.org/mailman/listinfo.cgi/boost-users or, via email, send a message with subject or body 'help' to boost-users-request(a)lists.boost.org You can reach the person managing the list at boost-users-owner(a)lists.boost.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Boost-users digest..." Today's Topics: 1. Accessing the Boost Sandbox (oranjsr(a)gmail.com) ---------------------------------------------------------------------- Message: 1 Date: Mon, 26 Aug 2024 10:00:58 -0400 From: <oranjsr(a)gmail.com> To: <boost-users(a)lists.boost.org> Subject: [Boost-users] Accessing the Boost Sandbox Message-ID: <010601daf7c0$60c585b0$22509110$(a)gmail.com> Content-Type: text/plain; charset="utf-8" Hi, I'm looking at a source forge project with the following required libraries: 1) Boost version 1.39 or later 2) TBB (Threading Building Blocks) version 2.1 or later 3) MSM (Meta State Machine) version 1.2 or later 4) Boost Logging Library v2 #3 appears to be in the boost sandbox Does boost sandbox still exists? Boost Sandbox When boost was developed using subversion, the Boost Sandbox contained unreviewed code that is intended to eventually become a part of the Boost libraries. New libraries should be developed separately as <https://svn.boost.org/trac/boost/wiki/ModularBoost> git modules, and existing projects should be <https://svn.boost.org/trac/boost/wiki/ExtractSandbox> moved to GitHub. The sandbox remains as a historical record. Accessing the Boost Sandbox The Boost Sandbox lives at <https://svn.boost.org/svn/boost/sandbox> https://svn.boost.org/svn/boost/sandbox within the old Boost Subversion repository. Regards Oran

2 1

[filesystem] why is this file not found?
by Michael Burr 04 Sep '24

04 Sep '24

I'm having difficulty using boost/filesystem.hpp on a simple test example. If I understand things correctly, this code should see if it can find the files called "test_file" and "test_file2" in the current directory. ``` #include <boost/filesystem.hpp> #include <iostream> using namespace boost::filesystem; int main() { path file1 = "test_file", file2 = "test_file2"; if(status(file1).type() == file_not_found) std::cout << "First file not found\n"; if(status(file2).type() == file_not_found) std::cout << "Second file not found\n"; return 0; } ``` If I run the following, ``` touch test_file g++ filesystem_check.cpp -lboost_filesystem ./a.out ``` the result is > First file not found > Second file not found I expected only the second file to be not found. I arrived at this question because exists(file1) was returning false when I thought it should return true, and I traced the issue back to this check. I've also tried this example with an absolute path, and the results were the same. This is using Boost 1.81 installed via macports on a mac with OS 12.5.1 (so slightly out-of-date OS). Is this a mac issue or am I missing something in my code?

2 1

Accessing the Boost Sandbox
by oranjsr＠gmail.com 26 Aug '24

26 Aug '24

Hi, I'm looking at a source forge project with the following required libraries: 1) Boost version 1.39 or later 2) TBB (Threading Building Blocks) version 2.1 or later 3) MSM (Meta State Machine) version 1.2 or later 4) Boost Logging Library v2 #3 appears to be in the boost sandbox Does boost sandbox still exists? Boost Sandbox When boost was developed using subversion, the Boost Sandbox contained unreviewed code that is intended to eventually become a part of the Boost libraries. New libraries should be developed separately as <https://svn.boost.org/trac/boost/wiki/ModularBoost> git modules, and existing projects should be <https://svn.boost.org/trac/boost/wiki/ExtractSandbox> moved to GitHub. The sandbox remains as a historical record. Accessing the Boost Sandbox The Boost Sandbox lives at <https://svn.boost.org/svn/boost/sandbox> https://svn.boost.org/svn/boost/sandbox within the old Boost Subversion repository. Regards Oran

1 0

Code using Boost::Compute builds fine on Linux, but not on Windows
by David Frischknecht 22 Aug '24

22 Aug '24

I wrote this simple program to learn how to use Boost::Compute. The program failed to build on Windows, but builds without any errors on Linux. If I modify the program to only operate on one vector, it works fine. On Windows I'm using vcpkg to pull in both Boost::Compute as well as the OpenCL SDK and I'm using Visual Studio 2022 to build the project. #define CL_TARGET_OPENCL_VERSION 300 #include <random> #include <vector> #include <boost/compute/core.hpp> #include <boost/compute/lambda.hpp> #include <boost/compute/algorithm/transform.hpp> #include <boost/compute/container/vector.hpp> std::mt19937 rng{ std::random_device()() }; std::uniform_int_distribution<> dist(1); namespace compute = boost::compute; using namespace boost::compute::lambda; int GetRandomNumber() { return dist(rng); } int main(int argc, char* argv[]) { const auto device = compute::system::default_device(); const compute::context context(device); compute::command_queue commandQueue(context, device); std::vector<int> hostVector1(10000); std::vector<int> hostVector2(10000); std::vector<int> hostResultVector(10000); std::ranges::generate(hostVector1, GetRandomNumber); std::ranges::generate(hostVector2, GetRandomNumber); compute::vector<int> deviceVector1(hostVector1.size(), context); compute::vector<int> deviceVector2(hostVector2.size(), context); compute::vector<int> deviceResultVector(hostResultVector.size(), context); compute::copy(hostVector1.begin(), hostVector1.end(), deviceVector1.begin(), commandQueue); compute::copy(hostVector2.begin(), hostVector2.end(), deviceVector2.begin(), commandQueue); transform(deviceVector1.begin(), deviceVector1.end(), deviceVector2.begin(), deviceResultVector.begin(), _1 + _2, commandQueue); compute::copy(deviceResultVector.begin(), deviceResultVector.end(), hostResultVector.begin(), commandQueue); return 0; } Here is the build output: Build started at 11:13 PM... 1>------ Build started: Project: BoostComputeTest, Configuration: Debug x64 ------ 1>Main.cpp 1>C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\iterator\transform_iterator.hpp(177,53): error C2039: 'get_buffer': is not a member of 'boost::compute::zip_iterator<boost::tuples::tuple<boost::compute::buffer_iterator<T>,boost::compute::buffer_iterator<T>,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>' 1>C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\iterator\transform_iterator.hpp(177,53): error C2039: with 1>C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\iterator\transform_iterator.hpp(177,53): error C2039: [ 1>C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\iterator\transform_iterator.hpp(177,53): error C2039: T=int 1>C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\iterator\transform_iterator.hpp(177,53): error C2039: ] 1>(compiling source file 'Main.cpp') 1> C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\iterator\zip_iterator.hpp(172,7): 1> see declaration of 'boost::compute::zip_iterator<boost::tuples::tuple<boost::compute::buffer_iterator<T>,boost::compute::buffer_iterator<T>,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>' 1> with 1> [ 1> T=int 1> ] 1> C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\iterator\transform_iterator.hpp(177,53): 1> the template instantiation context (the oldest one first) is 1> C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\Main.cpp(40,2): 1> see reference to function template instantiation 'OutputIterator boost::compute::transform<boost::compute::buffer_iterator<T>,boost::compute::buffer_iterator<T>,boost::compute::buffer_iterator<T>,boost::compute::lambda::expression<Expr>>(InputIterator1,InputIterator1,InputIterator2,OutputIterator,BinaryOperator,boost::compute::command_queue &)' being compiled 1> with 1> [ 1> OutputIterator=boost::compute::buffer_iterator<int>, 1> T=int, 1> Expr=boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::plus,boost::proto::argsns_::list2<const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<0>>,0>> &,const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<1>>,0>> &>,2>, 1> InputIterator1=boost::compute::buffer_iterator<int>, 1> InputIterator2=boost::compute::buffer_iterator<int>, 1> BinaryOperator=boost::compute::lambda::expression<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::plus,boost::proto::argsns_::list2<const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<0>>,0>> &,const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<1>>,0>> &>,2>> 1> ] 1> C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\algorithm\transform.hpp(75,12): 1> see reference to function template instantiation 'OutputIterator boost::compute::transform<boost::compute::zip_iterator<boost::tuples::tuple<boost::compute::buffer_iterator<T>,boost::compute::buffer_iterator<T>,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>,OutputIterator,boost::compute::detail::unpacked<BinaryOperator>>(InputIterator,InputIterator,OutputIterator,UnaryOperator,boost::compute::command_queue &)' being compiled 1> with 1> [ 1> OutputIterator=boost::compute::buffer_iterator<int>, 1> T=int, 1> BinaryOperator=boost::compute::lambda::expression<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::plus,boost::proto::argsns_::list2<const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<0>>,0>> &,const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<1>>,0>> &>,2>>, 1> InputIterator=boost::compute::zip_iterator<boost::tuples::tuple<boost::compute::buffer_iterator<int>,boost::compute::buffer_iterator<int>,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>, 1> UnaryOperator=boost::compute::detail::unpacked<boost::compute::lambda::expression<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::plus,boost::proto::argsns_::list2<const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<0>>,0>> &,const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<1>>,0>> &>,2>>> 1> ] 1> C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\algorithm\transform.hpp(48,34): 1> see reference to class template instantiation 'boost::compute::transform_iterator<InputIterator,UnaryOperator>' being compiled 1> with 1> [ 1> InputIterator=boost::compute::zip_iterator<boost::tuples::tuple<boost::compute::buffer_iterator<int>,boost::compute::buffer_iterator<int>,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>, 1> UnaryOperator=boost::compute::detail::unpacked<boost::compute::lambda::expression<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::plus,boost::proto::argsns_::list2<const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<0>>,0>> &,const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<1>>,0>> &>,2>>> 1> ] 1> C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\iterator\transform_iterator.hpp(175,15): 1> while compiling class template member function 'int boost::compute::transform_iterator<InputIterator,UnaryOperator>::dereference(void) const' 1> with 1> [ 1> InputIterator=boost::compute::zip_iterator<boost::tuples::tuple<boost::compute::buffer_iterator<int>,boost::compute::buffer_iterator<int>,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>, 1> UnaryOperator=boost::compute::detail::unpacked<boost::compute::lambda::expression<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::plus,boost::proto::argsns_::list2<const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<0>>,0>> &,const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<1>>,0>> &>,2>>> 1> ] 1> C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\iterator\iterator_facade.hpp(631,11): 1> see the first reference to 'boost::compute::transform_iterator<InputIterator,UnaryOperator>::dereference' in 'boost::iterators::iterator_core_access::dereference' 1> with 1> [ 1> InputIterator=boost::compute::zip_iterator<boost::tuples::tuple<boost::compute::buffer_iterator<int>,boost::compute::buffer_iterator<int>,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>, 1> UnaryOperator=boost::compute::detail::unpacked<boost::compute::lambda::expression<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::plus,boost::proto::argsns_::list2<const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<0>>,0>> &,const boost::compute::lambda::expression<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::compute::lambda::placeholder<1>>,0>> &>,2>>> 1> ] 1>C:\Users\Dave\source\repos\BoostComputeTest\BoostComputeTest\vcpkg_installed\x64-windows\x64-windows\include\boost\compute\iterator\transform_iterator.hpp(177,32): error C2530: 'context': references must be initialized 1>(compiling source file 'Main.cpp') 1>Done building project "BoostComputeTest.vcxproj" -- FAILED. ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== ========== Build completed at 11:13 PM and took 03.315 seconds ========== Is there something I'm missing from my project configuration on Windows? Thanks, Dave F.

1 0

Abwesenheitsnachricht: Re: [boost] [release] Boost.1.86.0
by Sören Textor 16 Aug '24

16 Aug '24

Derzeit bin ich nicht im Hause Ihre E-Mail wird nicht weitergeleitet. In dringenden Fällen bitte support(a)ditec-gmbh.de oder Telefonhotline +49-6221-31698-110 oder die Zentrale +49-6221-31698-0 kontaktieren. Mit freundlichen Grüßen Dr. Sören Textor ----------------------------------------------- DiTEC Dr. Siegfried Kahlich & Dierk Langer GmbH Im Breitspiel 19 | 69126 Heidelberg | Germany Handelsregister | Mannheim | HRB 341229 Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung. This document has to be treated confidentially. Its contents are not to be passed on, duplicated, exploited or disclosed without our express permission. All rights reserved, especially the right to apply for protective rights.

1 0

[release] Boost.1.86.0
by Marshall Clow 16 Aug '24

16 Aug '24

Release 1.86.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. The release contains numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.86.0> You can also download directly from: <https://archives.boost.io/release/1.86.0/source/> To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. -- The Boost Release Team Marshall Clow, Glen Fernandes, Ion Ion Gaztañaga

5 5

Boost in CUDA C++
by wickedPlatypus 12 Aug '24

12 Aug '24

Hi everyone: I have been using Boost for a couple of months in Ubuntu but I have moved into Windows 11 where I am using Microsoft VIsual Studio Community. I have been trying to run a simple code using the CUDA nvcc compiler but I am getting the next errors: [cid:09f3ea52-8ad8-4931-a32b-f178768de741] [cid:afc5117d-edf1-4262-be42-601516a4123d] I want to highlight that the code is working properly in C++. I have tested this code with the next configurations: -C++14 or C++17 or C++20 -CUDA ToolKit 12.5 or 12.6 -NVIDIA driver 560.81 -Microsoft VIsual Studio Community 2022 17.10.5 The first error message is related to the use of a compiler prior to C++ 20 but even using C++ 20 the error message is still present. Also, I have attached the code to this email. I really appreciate your expertise in this issue. Thank you so much in advance to all of you!!!

2 1

Program_Options library multitoken() question
by Keeling, William 06 Aug '24

06 Aug '24

Can the number of tokens be limited/validated? I am currently raising exception in notifier() function; if that is the only way, can the option name be known in the notifier function to improve my error message? Thanks William

1 0

undefined type on vs2008 but not vs2010
by Daniel 01 Aug '24

01 Aug '24

Hi, I'm new to C++, working on an old project using the vs2008 toolset. I need to add some networking and so I started with the docs tutorial "An asynchronous TCP daytime server". Boost 1.68 Error C2027 use of undefined type 'boost::_bi::add_cref<Pm,I>' BoostAsio d:\downloads\boost_1_68_0\boost\bind\bind.hpp 2323 namespace _bi {template< class Pm, int I > struct add_cref; ... template<class Pm, class A1> struct dm_result { typedef typename add_cref< Pm, 1 >::type type; <<< 2323 }; Do I need to provide more details? Thanks

2 1

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

26 Jul '24

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

1 0

error: template argument for template type parameter must be a type template< class Allocator = std::allocator< none > >
by Phil Phil 05 Jul '24

05 Jul '24

Greetings, I try to port a c++ project to a new environment with clang++-17, libcxx 17 and std=c++17 for x64 Linux. Also, I switched form boost 1.65 to 1.84. Now I start getting errors in boost itself: /workspace/usr/include/boost/statechart/fifo_worker.hpp:55:45: error: template argument for template type parameter must be a type 55 | template< class Allocator = std::allocator< none > > As far as I know this has to do with deprecation of some variable type in allocator. Any ideas how I might fix this on short notice? Regards

2 2

directory_iterator UNC path
by Lars Sunde 04 Jul '24

04 Jul '24

Hello, Using boost::filesystem::directory_iterator with an UNC path failed with Boost 1.84 and Windows 10. Did some research on this topic and found this bug report from 2022; https://github.com/boostorg/filesystem/issues/245 This issue contain a link to this fix; https://github.com/boostorg/filesystem/commit/9c9d127bddc2b72187c57f4933c49… When looking at boost 1.84 and 1.85 source code I cannot find the fix shown above. Please excuse my ignorance but what is the relationship between https://github.com/boostorg/filesystem and the sw released at https://www.boost.org<https://www.boost.org/> ? Kind regards, Lars [https://opengraph.githubassets.com/d5334b4df3942668241ead9dde0a136ddc1b0979…]<https://github.com/boostorg/filesystem> GitHub - boostorg/filesystem: Boost.org filesystem module<https://github.com/boostorg/filesystem> Boost.org filesystem module. Contribute to boostorg/filesystem development by creating an account on GitHub. github.com

2 2

Re: [Boost-users] Windows binaries, etc
by Michael Powell 30 Jun '24

30 Jun '24

Hello, Been a minute since I last updated my Boost libraries. Curious what the condition of the binaries is, re: VS2022 C++ compiler compatibility, alignment with current lang standards, such as this? https://boost.teeks99.com/bin/1.85.0/ As far as integration goes, I just add include and library paths to my projects, and on from there. Already more or less familiar with that aspect. Cheers, best, Michael W. Powell

2 1

boost-python - call c++ methods within another method with embedded Python ?
by Nicholas Yue 28 Jun '24

28 Jun '24

Hi I am trying to add an ability to allow for the calling of methods within a another method that is running an embedded python but I get an error saying "TypeError: No Python class registered for C++ class MyClass". #include <boost/python.hpp> class MyClass { public: MyClass() = default; void method1(); void method2(); void executePython(); }; #include <iostream> void MyClass::method1() { std::cout << "Method 1 called" << std::endl; } void MyClass::method2() { std::cout << "Method 2 called" << std::endl; } void MyClass::executePython() { try { Py_Initialize(); // Expose the current instance (self) to the embedded Python script boost::python::object main_namespace; main_namespace["self"] = boost::python::ptr(this); // Execute Python code that calls method1 and method2 on self boost::python::exec("self.method1()\nself.method2()", main_namespace); Py_Finalize(); } catch (boost::python::error_already_set&) { PyErr_Print(); } } int main() { MyClass mc; mc.executePython(); return 0; } -- Nicholas Yue https://www.linkedin.com/in/nicholasyue/

1 0

Fwd: [beast] Trying to Integrate Chunked Encoding into server-sync Example
by Max D 29 May '24

29 May '24

Hi everyone, I'm trying to integrate the manual chunked encoding example [0] into the sync-server example [1] and have difficulties understanding a compiler error. I thought I might find some help in this mailing list. Here's my diff to the original example: @@ -151,6 +151,22 @@ handle_request( req.method() != http::verb::head) return send(bad_request("Unknown HTTP-method")); + if (req.target().find("/chunked") == 0) { + std::vector<uint8_t> data; + for (int i = 0; i < 10; i++) { + data.push_back(0x00); + } + net::const_buffer buf {data.data(), 10}; + + send.send_chunk_headers(); + + for (int i = 0; i < 3; i++) { + send.send_chunk(buf); + } + + send.send_last_chunk(); + } + // Request path must be absolute and not contain "..". if( req.target().empty() || req.target()[0] != '/' || @@ -243,6 +259,29 @@ struct send_lambda http::serializer<isRequest, Body, Fields> sr{msg}; http::write(stream_, sr, ec_); } + + void + send_chunk_headers() + { + http::response<http::empty_body> res {http::status::ok, 11}; + res.set(http::field::server, "Beast"); + res.chunked(true); + + http::response_serializer<http::empty_body> sr{res}; + http::write_header(stream_, sr); + } + + void + send_last_chunk() + { + http::write(stream_, http::make_chunk_last()); + } + + void + send_chunk(net::const_buffer buf) const + { + http::write(stream_, http::make_chunk(buf)); + } }; // Handles an HTTP server connection I'm passing a TCP socket as well as the result of http::make_chunk() with a net::const_buffer to http::write() which, if I understand correctly, is the same thing that is done in the example. However, I'm getting the following error when compiling: .../server-sync/src/beast.cpp: In instantiation of ‘void send_lambda<Stream>::send_chunk(boost::asio::const_buffer) const [with Stream = boost::asio::basic_stream_socket<boost::asio::ip::tcp>]’: .../server-sync/src/beast.cpp:164:28: required from ‘void handle_request(boost::beast::string_view, boost::beast::http::request<Body, boost::beast::http::basic_fields<Allocator> >&&, Send&&) [with B ody = boost::beast::http::basic_string_body<char>; Allocator = std::allocator<char>; Send = send_lambda<boost::asio::basic_stream_socket<boost::asio::ip::tcp> >&; boost::beast::string_view = boost::basic_string_view<char, std::char_traits< char> >; boost::beast::http::request<Body, boost::beast::http::basic_fields<Allocator> > = boost::beast::http::message<true, boost::beast::http::basic_string_body<char>, boost::beast::http::basic_fields<std::allocator<char> > >]’ .../server-sync/src/beast.cpp:313:57: required from here .../server-sync/src/beast.cpp:283:20: error: no matching function for call to ‘write(boost::asio::basic_stream_socket<boost::asio::ip::tcp>&, boost::beast::http::chunk_body<boost::asio::const_buffer>) ’ 283 | http::write(stream_, http::make_chunk(buf)); | ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The same thing happens for the send_last_chunk() call. Why isn't the call to write() working? Did I misunderstand something in the example? I'm using boost 1.71 and am compiling with GCC 10.3.0. Let me know if you need any more details. Thanks in advance for any help Max --- [0] https://www.boost.org/doc/libs/1_71_0/libs/beast/doc/html/beast/using_http/… [1] https://www.boost.org/doc/libs/1_71_0/libs/beast/example/http/server/sync/h…

2 1

boost::flyweights::intermodule_holder
by Foelsche, Peter 10 May '24

10 May '24

Dear All, Thanks for the boost library! Apparently the boost::flyweight::intermodule_holder on LINUX is creating shared memory objects, which by accident (crash?) can persist after the process having created them is already gone. As a result I ran into the following situation: I could not successfully run some code, as it attempted to create an already existing shared memory object created by another user. Would the following be a solution to this problem: Use a copy of the code of the static_holder inside another namespace as attached and compile one module with __INCLUDE_HOLDER__ defined and all the rest without this define? Peter

4 4

Boost Graph - adjacency_list in_edge_iterator are only input_iterator_tag?
by Nic 10 May '24

10 May '24

Hi, Hopefully this is the right place for this. This with Boost 1.81.0 It looks like boost::adjacency_list's in_edge_iterator, out_edge_iterator, and for bidirectional graphs also edge_iterator all are only input iterators. This seems a bit restrictive, and is regardless of the type of EdgeList template parameter. For example, this code (which seems a relatively reasonable thing to want to do) doesn't work: https://godbolt.org/z/n3PdEYo49 It doesn't work because transform_view doesn't define iterator_category if the iterator is not at least a forward iterator (I'm a bit confused as to why that is, but that's not a boost-related thing). I did some digging and found out why the iterator is always an input iterator: The iterators are defined as following: template < class BaseIter, class VertexDescriptor, class EdgeDescriptor, class Difference > struct in_edge_iter : iterator_adaptor< in_edge_iter< BaseIter, VertexDescriptor, EdgeDescriptor, Difference >, BaseIter, EdgeDescriptor, use_default, EdgeDescriptor, Difference > { // .... }; EdgeDescriptor is passed in as the reference type, but it is not a reference so the iterator adaptor always chooses input_iterator_tag for the iterator_category. Does anyone know of a workaround, or know if this is the desired behavior for edge iterators? Am I missing something obvious here? Thank you very much, Nicolas Morales

2 1

boost.asio: random_access_file, io_uring and thread safety
by Matwey V. Kornilov 30 Apr '24

30 Apr '24

Hello, random_access_file is backed by the io_uring kernel interface on Linux. However, It is still unclear from Boost.Asio documentation, whether simultaneous parallel async_write_at in-flight requests are permitted by Asio? The queue of simultaneous requests is natively supported by io_uring. Is it still true for Asio? Is it also safe to fire parallel async_write_at from different threads? -- With best regards, Matwey V. Kornilov

1 0

Is there a buffered tcp stream in ASIO?
by accelerator0099 29 Apr '24

29 Apr '24

|Prepare a tcp server listening on [::]:23380, run the following code: #include <boost/asio.hpp> namespace io = boost::asio; using boost::system::system_error; int main() { try { io::io_context ctx; using io::ip::tcp; using io::buffer; tcp::socket s1(ctx); s1.connect(tcp::endpoint(io::ip::address_v4::loopback(), 23380)); for (size_t i{}; i != 10; ++i) io::write(s1, buffer("123", 3)); } catch (system_error& e) { return 1; } } strace says there are 10 syscalls: connect(6, {sa_family=AF_INET, sin_port=htons(23380), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 sendto(6, "123", 3, MSG_NOSIGNAL, NULL, 0) = 3 If I use boost::asio::ip::tcp::iostream: #include <boost/asio.hpp> namespace io = boost::asio; using boost::system::system_error; int main() { try { io::io_context ctx; using io::ip::tcp; using io::buffer; tcp::iostream s1{ tcp::socket(ctx) }; auto& nl = s1.socket(); nl.connect(tcp::endpoint(io::ip::address_v4::loopback(), 23380)); for (size_t i{}; i != 10; ++i) s1.write("123", 3); s1.flush(); } catch (system_error& e) { return 1; } } It does not make sense, still 10 syscalls: connect(6, {sa_family=AF_INET, sin_port=htons(23380), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 ioctl(6, FIONBIO, [1]) = 0 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="123", iov_len=3}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 3 Is there a stream in asio that could buffer the multiple and small pieces of data into one syscall? |

2 1

Difference in regex_replace replacement format handling between Boost.Regex and std::regex
by Josué Andrade Gomes 22 Apr '24

22 Apr '24

There is a difference in how the replacement format string is handled by regex_replace in Boost.Regex and std::regex. Consider the following example: #include <iostream>#include <regex>#include <boost/regex.hpp> int main() { std::string s{"a:b:c"}; std::string rx{":"}; std::string r{"\\$&"}; // Using std::regex std::string result_std = std::regex_replace(s, std::regex(rx), r); std::cout << "std::regex result: " << result_std << std::endl; // Outputs "a\:b\:c" // Using Boost.Regex std::string result_boost = boost::regex_replace(s, boost::regex(rx), r); std::cout << "Boost.Regex result: " << result_boost << std::endl; // Outputs "a$&b$&c" return 0; } std::regex result: a\:b\:c Boost.Regex result: a$&b$&c Affects Boost.Regex 1.84. I didn’t try other versions. Tested with GCC 13.2, clang 18.10 , cl 19.39.33523 and results are the same. Not tested with other versions. https://github.com/boostorg/regex/issues/210

1 0

Regarding a Vulnerability in Boost.Regex library
by kamallochan Jena 18 Apr '24

18 Apr '24

Hello everyone, Hope you all are doing well. There is a Vulnerability reported on Boost library as mentioned below. Any guidance or assistance or reply to this mail would be greatly appreciated. *Vulnerability ID:* BDSA-2018-2656 *Vulnerability Details:* Boost has a flaw in the function boost::re_detail_NUMBER::basic_regex_creator which can lead to a buffer over-read. An attacker can craft and send a malicious file which will trigger the buffer over-read, leading to a denial-of-service. Few query w.r.t boost::re_detail_NUMBER::basic_regex_creator() function: 1. Does Boost.Regex library or any Boost library internally use this function? 2. If the answer is yes, Which all libraries use this function? 3. Is this a known vulnerability and is it fixed in the latest Boost version? please provide some insights like (any change list or file name etc). Our project uses a boost library(which has file "boost/regex/v4/basic_regex_creator.hpp") and uses Boost.Regex library functions. *Should we be worried about this vulnerability (BDSA-2018-2656) affecting our code? * Thanks!

2 1

Any idea on CWE-704(BDSA-2018-1263) and CWE-126 (BDSA-2018-2656)
by kamallochan Jena 15 Apr '24

15 Apr '24

Dear all, Could someone assist me in determining if any version of Boost library is vulnerable to the following CWE? BDSA-2018-1263 CWE-704 and BDSA-2018-2656 CWE-126 Additionally, I would appreciate any details regarding these vulnerabilities, such as - the specific version of the Boost library where the vulnerability was identified - the name of the source code file, the exact line of code and function that causes the vulnerability - Whether the latest version of Boost includes a fix, and if so, which version of the library it was addressed in. Any guidance or assistance on this matter would be greatly appreciated. Thanks, Kjena

1 0

Re: [Boost-users] [beast] I can't write a hello world server
by Senthil Cheetancheri 10 Apr '24

10 Apr '24

(Trying to repost because the previous message was rejected due to size limits.) Hi Loup, The reason I'm taking the time to ask here is because I feel there is something fundamental, likely obvious to the experts, that I don't understand about how beast (and, I'm guessing, asio) works, and how I'm supposed to use it. It seems like you are quite comfortable with C++. That is good because it is a necessary background for this. Boost.Asio and .Beast are inherently advanced topics. The examples use quite advanced C++ knowledge. It could appear simple to experts who understand asio and C++, as well as to newcomers if they were lucky to get the right orientation when they began to learn C++. I had to unlearn a lot of 'C' and old C++ notions. Here are some resources that helped me reach the Aha! moment after a lot of struggles. They are all well worth the patient time you will need. (They are from my bookmarks and are a bit dated. You can easily get the corresponding latest versions.) 1. ASIO: https://www.boost.org/doc/libs/1_79_0/doc/html/boost_asio.html 2. Beast: Watch this video https://youtu.be/7FQwAjELMek at the bottom of the tutorials page https://www.boost.org/doc/libs/1_80_0/libs/beast/doc/html/beast/examples.ht…. This video was a turning point for me. 3. If you would like interactive help, join the #beast channel of the cpplang slack https://cppalliance.org/slack/. They are very kind and super helpful. When you get asio and beast to work well, they are beautiful and give you joy. HTH. Thanks, Senthil.

2 3