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

Using Boost in CLR Class
by 임성준 09 Jan '24

09 Jan '24

Hello, I have question about using Boost. I'm trying to using boost in clr class of Visual Studito 2022 When I build the project, I got following error Error C1189 #error: "This library now requires a C++11 or later compiler - this message was generated as a result of BOOST_NO_CXX11_REF_QUALIFIERS being set" ClassLibrary2 C:\Users\bussly\source\repos\ClassLibrary2\packages\boost.1.84.0\lib\native\include\boost\multiprecision\detail\check_cpp11_config.hpp 34 Error (active) E0035 #error directive: "This library now requires a C++11 or later compiler - this message was generated as a result of BOOST_NO_CXX11_REF_QUALIFIERS being set" ClassLibrary2 C:\Users\bussly\source\repos\ClassLibrary2\packages\boost.1.84.0\lib\native\include\boost\multiprecision\detail\check_cpp11_config.hpp 58 Even I didn't make any code, just add an include boost header. Following is the scenario of what I did - Visual Studio 2022 - Create new project -> CLR Class Library(.Net Framework) - Install NuGet Package -> boost 1.84.0 - Add include boost -> #include "boost/geometry.hpp" - Build solution - Error and following is properties of my project - Platform Toolset: Visual Studio 2022(v143) - C++ Language Standard: ISO C++ 20 Standard(/std:c++20) - C Language Standard: Default(Legacy MSVC) I tried with C++ 14 and C++ 17 also, but failed. Can I get any solution for this? Thank you.

1 0

[Boost.Redis] Single Connection Concurrency Inquiry
by Samarah Uriarte 08 Jan '24

08 Jan '24

Hello, I am using the Boost Redis library to write to a local Redis server and would like to inquire about how a single connection can handle concurrent calls. I have several C++ classes that have their own Boost.Redis connections, but this is leading to ASIO-related hanging behavior that is difficult to debug. I would like to simplify the design by initializing only one connection that can be used by all of these classes instead. I know the "async_exec" method supports concurrency but I wonder if this might cause any future issues with larger workloads. Thank you in advance. Sincerely, Samarah Uriarte

1 0

Problems downloading boost on Linux
by Gonzalo Garramuño 01 Jan '24

01 Jan '24

I have tried downloading boost 1.76 on Linux from Argentina with: curl -# -L -o boost_1_76_0.zip.tmp https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76… and also from the boost web page. This leads to a redirect to JFrog. I tried creating an account with both Google (which led to Invalid credentials - you might not be a registered MyJFrog user. Please try again. ) and with a new account on JFrog which sent me an email requesting my company: To confirm this request, please include the license owner or any other support contact associated with your company's subscription approval in this email thread. Are the boost libraries at www.boost.org available for free or only under subscription? I found I can still download them from sourceforge, of course, but I would need to patch any dependencies that point to the older web-site. -- Gonzalo Garramuño ggarra13(a)gmail.com

2 2

Cobalt link error
by Josué Andrade Gomes 23 Dec '23

23 Dec '23

I'm trying to build a minimal Cobalt library sample. I'm getting link errors: Build and installed Boost with: ./bootstrap.sh --prefix=$HOME/.local ./b2 install Sample: #include <boost/cobalt.hpp> #include <iostream> boost::cobalt::main co_main(int, char *[]) { std::cout << "Hello world\n"; co_return 0; } CMakeLists.txt cmake_minimum_required(VERSION 3.20) project(coro_study) set(CMAKE_EXPORT_COMPILE_COMMANDS ON) set(CMAKE_CXX_STANDARD 20) set(CMAKE_VERBOSE_MAKEFILE ON) set(Boost_VERBOSE 1) set(Boost_DEBUG 1) find_package(Boost REQUIRED COMPONENTS system) add_executable(sample sample.cpp) target_include_directories(sample4 PRIVATE ${Boost_INCLUDE_DIRS}) target_link_libraries(sample4 PRIVATE ${Boost_LIBRARIES}) cmake output: dev ~/Projects/coroutines/x64-linux-debug $ cmake .. -- The C compiler identification is GNU 11.4.0 -- The CXX compiler identification is GNU 11.4.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Boost 1.84.0 at /home/dev/.local/lib/cmake/Boost-1.84.0 -- Requested configuration: QUIET REQUIRED COMPONENTS system -- BoostConfig: find_package(boost_headers 1.84.0 EXACT CONFIG REQUIRED QUIET HINTS /home/dev/.local/lib/cmake) -- Found boost_headers 1.84.0 at /home/dev/.local/lib/cmake/boost_headers-1.84.0 -- BoostConfig: find_package(boost_system 1.84.0 EXACT CONFIG REQUIRED QUIET HINTS /home/dev/.local/lib/cmake) -- Found boost_system 1.84.0 at /home/dev/.local/lib/cmake/boost_system-1.84.0 -- Boost toolset is gcc11 (GNU 11.4.0) -- Scanning /home/dev/.local/lib/cmake/boost_system-1.84.0/libboost_system-variant*.cmake -- Including /home/dev/.local/lib/cmake/boost_system-1.84.0/libboost_system-variant-shared.cmake -- [x] libboost_system.so.1.84.0 -- Including /home/dev/.local/lib/cmake/boost_system-1.84.0/libboost_system-variant-static.cmake -- [ ] libboost_system.a -- Adding boost_system dependencies: headers -- Found Boost: /home/dev/.local/lib/cmake/Boost-1.84.0/BoostConfig.cmake (found version "1.84.0") found components: system -- Configuring done -- Generating done -- Build files have been written to: /home/dev/Projects/coroutines/x64-linux-debug make output: dev ~/Projects/coroutines/x64-linux-debug $ make /usr/bin/cmake -S/home/dev/Projects/coroutines -B/home/dev/Projects/coroutines/x64-linux-debug --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /home/dev/Projects/coroutines/x64-linux-debug/CMakeFiles /home/dev/Projects/coroutines/x64-linux-debug//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[1]: Entering directory '/home/dev/Projects/coroutines/x64-linux-debug' make -f CMakeFiles/sample4.dir/build.make CMakeFiles/sample4.dir/depend make[2]: Entering directory '/home/dev/Projects/coroutines/x64-linux-debug' cd /home/dev/Projects/coroutines/x64-linux-debug && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/dev/Projects/coroutines /home/dev/Projects/coroutines /home/dev/Projects/coroutines/x64-linux-debug /home/dev/Projects/coroutines/x64-linux-debug /home/dev/Projects/coroutines/x64-linux-debug/CMakeFiles/sample4.dir/DependInfo.cmake --color= make[2]: Leaving directory '/home/dev/Projects/coroutines/x64-linux-debug' make -f CMakeFiles/sample4.dir/build.make CMakeFiles/sample4.dir/build make[2]: Entering directory '/home/dev/Projects/coroutines/x64-linux-debug' [ 50%] Building CXX object CMakeFiles/sample4.dir/sample4.cpp.o /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -isystem /home/dev/.local/include -std=gnu++20 -MD -MT CMakeFiles/sample4.dir/sample4.cpp.o -MF CMakeFiles/sample4.dir/sample4.cpp.o.d -o CMakeFiles/sample4.dir/sample4.cpp.o -c /home/dev/Projects/coroutines/sample4.cpp [100%] Linking CXX executable sample4 /usr/bin/cmake -E cmake_link_script CMakeFiles/sample4.dir/link.txt --verbose=1 /usr/bin/c++ CMakeFiles/sample4.dir/sample4.cpp.o -o sample4 /home/dev/.local/lib/libboost_system.so.1.84.0 /usr/bin/ld: CMakeFiles/sample4.dir/sample4.cpp.o: in function `co_main(co_main(int, char**)::_Z7co_mainiPPc.Frame*) [clone .actor]': sample4.cpp:(.text+0x2a9): undefined reference to `boost::cobalt::detail::main_promise::final_suspend()' /usr/bin/ld: CMakeFiles/sample4.dir/sample4.cpp.o: in function `main::reset_res::operator()(std::pmr::memory_resource*)': sample4.cpp:(.text._ZZ4mainEN9reset_resclEPNSt3pmr15memory_resourceE[_ZZ4mainEN9reset_resclEPNSt3pmr15memory_resourceE]+0x1c): undefined reference to `boost::cobalt::this_thread::set_default_resource(std::pmr::memory_resource*)' /usr/bin/ld: CMakeFiles/sample4.dir/sample4.cpp.o: in function `main': sample4.cpp:(.text.main[main]+0x5b): undefined reference to `boost::cobalt::this_thread::set_default_resource(std::pmr::memory_resource*)' /usr/bin/ld: sample4.cpp:(.text.main[main]+0xc2): undefined reference to `boost::cobalt::detail::main_promise::run_main(boost::cobalt::main)' /usr/bin/ld: CMakeFiles/sample4.dir/sample4.cpp.o: in function `bool boost::cobalt::detail::promise_receiver<void>::awaitable::await_suspend<boost::cobalt::detail::fork::promise_type>(std::__n4861::coroutine_handle<boost::cobalt::detail::fork::promise_type>)': sample4.cpp:(.text._ZN5boost6cobalt6detail16promise_receiverIvE9awaitable13await_suspendINS1_4fork12promise_typeEEEbNSt7__n486116coroutine_handleIT_EE[_ZN5boost6cobalt6detail16promise_receiverIvE9awaitable13await_suspendINS1_4fork12promise_typeEEEbNSt7__n486116coroutine_handleIT_EE]+0x7f): undefined reference to `boost::cobalt::detail::already_awaited()' /usr/bin/ld: CMakeFiles/sample4.dir/sample4.cpp.o: in function `boost::cobalt::detail::promise_receiver<void>::awaitable::interrupt_await() &': sample4.cpp:(.text._ZNR5boost6cobalt6detail16promise_receiverIvE9awaitable15interrupt_awaitEv[_ZNR5boost6cobalt6detail16promise_receiverIvE9awaitable15interrupt_awaitEv]+0x33): undefined reference to `boost::cobalt::detail::detached_exception()' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/sample4.dir/build.make:101: sample4] Error 1 make[2]: Leaving directory '/home/dev/Projects/coroutines/x64-linux-debug' make[1]: *** [CMakeFiles/Makefile2:86: CMakeFiles/sample4.dir/all] Error 2 make[1]: Leaving directory '/home/dev/Projects/coroutines/x64-linux-debug' make: *** [Makefile:94: all] Error 2

3 4

Handshake Error 10009
by Jens Kallup 23 Dec '23

23 Dec '23

Hello, I tried use the boost::asio to create a SSL-Server, but I fail. The Code I used is attached to this Text. acceptor_ and context_ give me true result, but the start_accept() methode give me a Handshake-Error: 10009 (invalid descriptor handle). How can I avoid this, and how can I fix the Code in the right point ? Thanks for reading paule32 // ----------------------------------------------------------------- // File: BoostServer.cc // Author: (c) 2023 Jens Kallup - paule32 // All rights reserved // // only for education, and non-profit usage ! // ----------------------------------------------------------------- # include <stdio.h> # include <stdlib.h> # include <sys/types.h> # include <iostream> # include <string> # include <functional> # include <thread> # include <memory> # include <boost/asio.hpp> # include <boost/asio/ssl.hpp> using namespace boost::asio; using namespace std; // ----------------------------------------------------------------- // @brief namespace name for Version 1.0.0 of our project ... // ----------------------------------------------------------------- namespace dBaseRelease { std::string ApplicationExeName; // ----------------------------------------------------------------- // @brief This member handle the exception message text that is use // to "try catch" exception's during the runtime of the // application. // // @param std::string& message - The e.what() message. // @return nothing // // @since dBaseRelease // @author paule32 // ----------------------------------------------------------------- void handle_exception(const std::string& message) { std::string error_message; for (int len = 0; len < message.length(); ++len) { if (message[len] == '[') break; error_message.push_back(message[len]); } std::cerr << "Exception " << error_message << std::endl; } class SSLServer: public std::enable_shared_from_this<SSLServer> { public: SSLServer(io_service& service, uint16_t port): acceptor_(service, ip::tcp::endpoint(ip::tcp::v4(), port)), context_ (ssl::context::tlsv12) { context_.set_options( ssl::context::default_workarounds | ssl::context::sslv2 | ssl::context::sslv3 | ssl::context::tlsv12); if (isAcceptorInitialized() && isContextInitialized ()) { std::cout << "acceptor ok" << std::endl; std::cout << "context ok" << std::endl; start_accept(); } else { std::cout << "server init error" << std::endl; } } private: void start_accept() { ssl_socket_ = std::make_shared<ssl::stream<ip::tcp::socket> >(acceptor_.get_executor(), context_); // ---------------------------------- // Starte den asynchronen Handshake // ---------------------------------- ssl_socket_->async_handshake(ssl::stream_base::server, [this](const boost::system::error_code& error) { if (!error) { // ----------------------------------- // Wenn der Handshake erfolgreich ist, // akzeptiere die Verbindung // ----------------------------------- if (ssl_socket_ && ssl_socket_->lowest_layer().is_open()) { std::cout << "SSL-Handshake erfolgreich und verbunden." << std::endl; acceptor_.async_accept(ssl_socket_->lowest_layer(), [this](const boost::system::error_code& accept_error) { if (!accept_error) { handle_client(); } else { std::cerr << "Accept error: " << accept_error.message() << std::endl; } }); } else { std::cerr << "SSL-Handshake erfolgreich, aber Verbindung nicht geöffnet." << std::endl; } } else { std::cerr << "Handshake error: " << error.message() << " (" << error.value() << ")" << std::endl; } }); } void handle_client() { // ------------------------------------ // Lese/Schreibe Daten mit ssl_socket_ // ------------------------------------ boost::asio::async_read_until(*ssl_socket_, buffer_, '\n', [this](const boost::system::error_code& read_error, std::size_t bytes_transferred) { if (!read_error) { std::istream is(&buffer_); std::string received_data; std::getline(is, received_data); std::cout << "Received data from client: " << received_data << std::endl; // ----------------------------------------- // Hier kannst du auf die empfangenen Daten // reagieren und die Antwort vorbereiten // ----------------------------------------- std::string response = "Hello from the server!\n"; // ----------------------------------------- // Sende die Antwort an den Client // ----------------------------------------- boost::asio::async_write(*ssl_socket_, boost::asio::buffer(response), [this](const boost::system::error_code& write_error, std::size_t) { if (!write_error) { // ----------------------------- // Schließe die Verbindung // ----------------------------- ssl_socket_->lowest_layer().close(); // ----------------------------- // Starte die nächste Akzeptanz // ----------------------------- start_accept(); } else { std::cerr << "Write error: " << write_error.message() << std::endl; } }); } else { std::cerr << "Read error: " << read_error.message() << std::endl; } }); } // ------------------------------------------------ // Überprüfung, ob der Acceptor initialisiert wurde // ------------------------------------------------ bool isAcceptorInitialized() const { return acceptor_.is_open(); } // ------------------------------------------------ // Überprüfung, ob der Context initialisiert wurde // ------------------------------------------------ bool isContextInitialized() { try { // ---------------------------------- // load certificate, and private key // ---------------------------------- context_.use_certificate_chain_file("server.crt.pem"); context_.use_private_key_file("server.key.pem", ssl::context::pem); return true; } catch (const boost::system::system_error& e) { handle_exception(e.what()); return false; } } private: ip::tcp::acceptor acceptor_; ssl::context context_; std::shared_ptr<ssl::stream<ip::tcp::socket>> ssl_socket_; boost::asio::streambuf buffer_; }; } // namespace: dBaseRelease int main(int argc, char **argv) { using namespace dBaseRelease; try { ApplicationExeName = argv[0]; io_service service; std::shared_ptr<SSLServer> server = std::make_shared<SSLServer>(service, 12345); service.run(); } catch (const std::exception& e) { std::cerr << "Exception: " << e.what() << std::endl; return EXIT_FAILURE; } return EXIT_SUCCESS; } -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft. www.avast.com

1 0

Abwesenheitsnachricht: Re: Cobalt link error
by Sören Textor 23 Dec '23

23 Dec '23

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

Boost Asio Multicast
by Georg Gast 18 Dec '23

18 Dec '23

Hi there, I wrote an application that is to a good part based on https://www.boost.org/doc/libs/1_83_0/doc/html/boost_asio/example/cpp11/mul… https://www.boost.org/doc/libs/1_83_0/doc/html/boost_asio/example/cpp11/mul… It worked OK on my laptop as the packages arrived in my vm and my host. As we tried it on real machines the packages did not arrive. (all windows machines). With *netsh interface ip show joins* I could see on my laptop that the join was on the ethernet card. On the real machines it choose "the wrong" network card. I tried with "outbound_interface" to change it but didn't work... It's all ipv4. Can or should I use a static route to get the packages into the right net segment? Bye Georg

2 1

[Boost.Asio] Asynchronous queue?
by accelerator0099 16 Dec '23

16 Dec '23

Consider the producer-consumer model: producer -+- consumer1 +- consumer2 +- consumer3 +- consumer4 +- consumer5 The producer periodly push items into a queue, and those consumers wait on that queue for items It's easy to implement in a synchronous, multi-threaded environment: the producer just locks the queue and push into it, and notify one consumer through a condition variable. Consumers waiting on that condition variable will be woken one by one, popping items and consume them How to do those in a asynchronous environment? Consumers async_pop() on that queue, posting their completion tokens into the executor. When there are items available, the executor notify one consumer by calling its completion token Is it right? How do the producer tell the executor "The asynchronous operation is done, You should call that completion token"? My implemention of a possible async queue (based on timers): #include <boost/asio.hpp> #include <deque> #include <iostream> using namespace std::literals; namespace io = boost::asio; using io::awaitable; auto& uawait = io::use_awaitable; template<class D> awaitable<void> delay(const D& dur) { io::steady_timer tm{ co_await io::this_coro::executor }; tm.expires_after(dur); co_await tm.async_wait(uawait); } template<class T> class aqueue { std::deque<T> mq; public: using reference = T&; using const_reference = const T&; size_t size() const noexcept { return mq.size(); } bool empty() const noexcept { return mq.empty(); } awaitable<T> async_pop() { while (empty()) { co_await delay(1ms); } auto t = std::move(mq.front()); mq.pop_front(); co_return t; } awaitable<void> async_push(T t) { mq.push_back(std::move(t)); co_return; } }; class consumer { public: const int id; aqueue<int>& queue; consumer(int _i, aqueue<int>& _q) : id{ _i }, queue{ _q } {} awaitable<void> operator()() { std::cout << "Consumer " << id << " started\n"; auto i = co_await queue.async_pop(); std::cout << "Consumer " << id << " got " < aq; auto producer = [&]() -> awaitable<void> { std::cout << "Producer started\n"; for (int i{}; i != 5; ++i) { co_await delay(1s); co_await aq.async_push(i); } }; io::co_spawn(ctx, producer, io::detached); for (int i{}; i != 5; ++i) io::co_spawn(ctx, consumer{ i, aq }, io::detached); std::cout << "RUN\n"; ctx.run(); return 0; } Is it a proper way to do so using timers? I think there should be a better way

3 2

Fin boost with cmake in config mode
by Alain O' Miniussi 15 Dec '23

15 Dec '23

Hi, I'd like to find Boost 1.84 from cmake 3.28 in config mode (https://cmake.org/cmake/help/latest/command/find_package.html#id6) My Boost distribution is in a non standard location <mypath> meaning, IF i UNDERSTAND CORRECTLY, that cmake will try to set Boost_DIR to <mypath>/lib/cmake/Boost-1.84.0/BoostConfig.cmake. Which environnement should I set so that it works ? Thanks ---- Alain Miniussi DSI, Pôles Calcul et Genie Log. Observatoire de la Côte d'Azur Tél. : +33609650665

2 1

Cobalt documentation error
by Josué Andrade Gomes 14 Dec '23

14 Dec '23

I’m seeing the following error while browsing the recently released Cobalt library documentation [1]: Failed to generate image: mmdc failed: Error: Failed to launch the browser process! /root/.cache/puppeteer/chrome/linux-1108766/chrome-linux/chrome: error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file: No such file or directory TROUBLESHOOTING: https://pptr.dev/troubleshooting at Interface.onClose (file:///root/.nvm/versions/node/v18.18.1/lib/node_modules/@mermaid-js/mermaid-cli/node_modules/@puppeteer/browsers/lib/esm/launch.js:253:24) at Interface.emit (node:events:529:35) at Interface.close (node:internal/readline/interface:534:10) at Socket.onend (node:internal/readline/interface:260:10) at Socket.emit (node:events:529:35) at endReadableNT (node:internal/streams/readable:1368:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) [1] https://www.boost.org/doc/libs/1_84_0/libs/cobalt/doc/html/index.html

1 0

Re: [Boost-users] Could sprintf be replaced with snprintf?
by Matt Borland 14 Dec '23

14 Dec '23

> On Dec 13, 2023, at 9:32 PM, Karsten Ahnert <karsten.ahnert(a)gmx.de> wrote: > > Yes, please go on. It would be great if odeint will be maintained in the future. Thank you! > > What are your GitHub user names? I can add you as maintainer but I want to be sure to use right name and avoid a potential name collision. > > Karsten Karsten, My GitHub username is mborland (https://github.com/mborland) and Nick is NAThompson (https://github.com/NAThompson) Let me know if you need anything else. Thanks, Matt

1 0

[release] Boost 1.84.0
by Marshall Clow 14 Dec '23

14 Dec '23

Release 1.84.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. This release contain two new libraries, numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.84.0> You can also download directly from: <https://boostorg.jfrog.io/artifactory/main/release/1.84.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

1 0

Re: [Boost-users] Could sprintf be replaced with snprintf?
by McGrath, Justin M 13 Dec '23

13 Dec '23

Has there been any movement on having someone else maintain ODEINT? I don't know that I would be of much use, but I'm willing to help where I can. There is one other issue that isn't critical, but it would save our group from having to do some hand editing of ODEINT for use with our project. Some of the paths are long enough that after they're included in our project they have nonportable lengths, requiring use to rename them. I made an issue last year: https://github.com/boostorg/odeint/issues/54. Changing the names would surely break code, and I don't know if this is a feasible change. Given that it's pretty easy for people to update include directives though, maybe it's not too intrusive. If it's a welcome change, I can submit a PR on GitHub. Best wishes, Justin ________________________________________ From: McGrath, Justin M <jmcgrath(a)illinois.edu> Sent: Monday, December 4, 2023 11:53 AM To: Matt Borland; Karsten Ahnert Cc: mario.mulansky(a)gmx.net; Nick Thompson Subject: Re: [Boost-users] Could sprintf be replaced with snprintf? Thank you everyone. It would be great if someone could continue managing the package. It's a great resource. Best wishes, Justin ________________________________________ From: Matt Borland <matt(a)mattborland.com> Sent: Friday, December 1, 2023 2:04 AM To: Karsten Ahnert Cc: McGrath, Justin M; mario.mulansky(a)gmx.net; Nick Thompson Subject: Re: [Boost-users] Could sprintf be replaced with snprintf? > On Nov 30, 2023, at 9:27 PM, Karsten Ahnert <karsten.ahnert(a)gmx.de> wrote: > > Merged the pull request. We are not actively maintaining the library anymore. > > But I will keep an eye on any upcoming changes. > Karsten, Thanks. Would you be interested in new maintainers stepping in for the library? Nick Thompson (cced) and I are maintainers on several other Boost libraries (math, multiprecision, random, and test), and we would be interested in helping out. He’s a mathematician, and I am a full-time Boost developer. If you would like to schedule a call or anything to discuss we can do that. Matt

3 2

coroutine condition_variable
by Keith Bennett 07 Dec '23

07 Dec '23

I'm using asio's awaitable. Couroutines are pretty neat. One of the things that keeps cropping up in the ability to notify another function that something has finished. In the past, I would use condition_variable and wait on that. Is there a better way to do that with coroutines? eg, I want to do something like: asio::awaitable<void> function(std::mutex& mtx, condition_variable& cv) { std::unique_lock lock{mtx}; // suspend this function until notified or 30 seconds expired auto expired = co_await cv.wait_until(lock, std::chrono::seconds(30)); if (expired) { // or something log("expired"); co_return; } do_some_work(); } then somewhere else I might do: asio::awaitable<void> somewhere_else(condition_variable& cv) { do_other_work(); cv.notify_one(); } I understand that it's a bad idea to hold a lock during co_await. What other problems prevent something like this from being created? Does something like this already exist? It's not clear from asio reference. I'm using boost 1.81.0 but I can upgrade if that is a problem -- Keith Bennett

3 8

[python] to_python_converter , is by value needed?
by MM 04 Dec '23

04 Dec '23

Hello, I have posted a question here some time ago, I thought to try here as well https://stackoverflow.com/questions/77552946/to-python-converter-is-by-valu… The community of experts in boost.python seems to have moved off to other concerns? Rds,

1 0

Could sprintf be replaced with snprintf?
by McGrath, Justin M 30 Nov '23

30 Nov '23

I am using some Boost libraries in a code base that does not want any use of sprintf. An automatic test flags any calls to it or vsprintf. Is it possible to replace all uses of sprintf with snprintf? I really doubt there are actually any security issues here, but I'm hoping this wouldn't be too difficult or cause any problems other than the effort to do it. Cheers, Justin

2 6

[Boost.Test] Saving Context Information for Failed Test Cases
by Bingtao Yin 16 Nov '23

16 Nov '23

I am a user of Boost.Test, and I am currently looking for a way to record some context information when dealing with failed test cases. Specifically, I would like to save certain variables to a file to facilitate debugging Could you please advise on any methods or recommendations within Boost.Test to fulfill this requirement? Are there any best practices or example code snippets that you could share? Thank you very much for your assistance! Best regards,

1 0

Re: [Boost-users] Problem with named_mutex on Windows
by David C. Partridge 15 Nov '23

15 Nov '23

I just realised it's not hanging - it's thrown an interprocess exception. I have revised my code to capture and report on that. I will let you know what it says. David From: David C. Partridge <david.partridge(a)perdrix.co.uk> Sent: 13 November 2023 14:16 To: 'boost-users(a)lists.boost.org' <boost-users(a)lists.boost.org> Subject: Problem with named_mutex on Windows I have a user reporting that the following code in my application's main() hangs unless he uses "Run as Adminstrator": ZTRACE_RUNTIME("Checking Mutex"); bip::named_mutex dssMutex{ bip::open_or_create, "DeepSkyStacker.Mutex.UniqueID.12354687" }; bip::scoped_lock<bip::named_mutex> lk(dssMutex, bip::defer_lock); const bool firstInstance{ lk.try_lock() }; ZTRACE_RUNTIME(" firstInstance: %s", firstInstance ? "true" : "false"); The trace shows "Checking mutex" and then it all stops. Is my code in error and if so what do I need to change? If not, how can I determine what the problem is? On a related issue: I think that this is C++ Exception safe, as the mutex will be unlocked and deleted. However, if a C exception occurs then how should I clean up? Is the named_mutex persistent over reboots? If so, where is it held (in case I need to do a manual cleanup). Many thanks David

1 1

Problem with named_mutex on Windows
by David C. Partridge 13 Nov '23

13 Nov '23

I have a user reporting that the following code in my application's main() hangs unless he uses "Run as Adminstrator": ZTRACE_RUNTIME("Checking Mutex"); bip::named_mutex dssMutex{ bip::open_or_create, "DeepSkyStacker.Mutex.UniqueID.12354687" }; bip::scoped_lock<bip::named_mutex> lk(dssMutex, bip::defer_lock); const bool firstInstance{ lk.try_lock() }; ZTRACE_RUNTIME(" firstInstance: %s", firstInstance ? "true" : "false"); The trace shows "Checking mutex" and then it all stops. Is my code in error and if so what do I need to change? If not, how can I determine what the problem is? On a related issue: I think that this is C++ Exception safe, as the mutex will be unlocked and deleted. However, if a C exception occurs then how should I clean up? Is the named_mutex persistent over reboots? If so, where is it held (in case I need to do a manual cleanup). Many thanks David

1 0

Optimizing serialization of std containers
by Gidi Gal 05 Nov '23

05 Nov '23

Hello, Are there any settings or additional code required to optimize the serialization of std containers ? I serialize a nested container: std::vector<std::deque<int>>. The max size of each deque entry is 20. I include boost/serialization/deque.hpp and boost/serialization/vector.hpp and I serialize the container in the following way: std::ofstream ofs(outFileName); boost::archive::binary_oarchive oa(ofs); oa << data; I created data with 10600 integers in the deque. The size of the serialized output file is 54493. Now, I test an alternate serialization. I serialized the size of the vector and then per each entry I serialize its size, which cannot be more than 20, so char is enough for that, next I serialize the integers in this entry. The size of the serialized output file is 43484. Is there a way to achieve better results for the default serialization ? Thanks, Gidi

1 0

why diagnostic_information is std::exception::what: Unknown exception
by Bernard 30 Oct '23

30 Oct '23

greetings kind regards may i please inquire how not to obtain "std::exception::what: Unknown exception" from diagnosic_inforumation() . my meaning is to inquire how to obtain as per example on boost web page https://www.boost.org/doc/libs/1_83_0/libs/exception/doc/tutorial_diagnosti… output : "std::exception::what: example_io error" id est where did "example_io error" come from as neither boost::exception nor std:::exception accept constructor string arguments . please my code below . thank you kindly #include "stl" // #includes all stl #include files #include "boost\exception\all.hpp" using namespace std; struct ceXception : virtual boost::exception, virtual std::exception { using this_type = ceXception; ceXception() {} auto what() { cerr << __FUNCSIG__ << endl; return string("return from " + string(__FUNCSIG__)); } template<typename charType> friend std::basic_ostream<charType>& operator<<(std::basic_ostream<charType>& _ostream, const this_type&) { cerr << "to cerr from " << __FUNCSIG__ << endl; _ostream << "to ostream from " << __FUNCSIG__ << endl; return _ostream; } }; void foo() { try { BOOST_THROW_EXCEPTION(ceXception()); } catch (ceXception& e) { cerr << boost::diagnostic_information(e); } } int main() { foo(); return 0; }

2 2

Async review scheduled for September 22, 2023 - October 2, 2023
by Mateusz Loskot 07 Sep '23

07 Sep '23

Hi, Following request from Nial and Klemens, we have scheduled new round of the Async review for September 22, 2023 - October 2, 2023 https://www.boost.org/community/review_schedule.html Best regards, -- Mateusz Loskot, on behalf of the Review Wizards

1 0

Error LNK1104 cannot open file 'boost_unit_test_framework-vc143-mt-x64-1_82.lib' cal_data_gain_pwr_test C:\Users\mushtaq.syed\Downloads\uhd-master\host\build\tests\LINK 1
by Mushtaq A. Syed, Ph.D. 28 Aug '23

28 Aug '23

Hi: My project uses the Boost library. I have installed C:\Program Files\Boost\boost_1_82_0. I also built using the bootstrap and .\b2 commands from the command window. This was because all the libboost libraries in C:\Program Files\Boost\boost_1_82_0\stage\lib were missing. Now when I build my code using Visual Studio 2022, I am getting the above error. I searched my Boost root folder and cannot find boost_unit_test_framework-vc143-mt-x64-1_82.lib; however, I do see libboost_unit_test_framework-vc143-mt-x64-1_82.lib and other libboost libraries but not a single boost library. I don’t know why it is looking for boost_unit_test_framework-vc143-mt-x64-1_82.lib and not libboost_unit_test_framework-vc143-mt-x64-1_82.lib. Could you please help resolve this? Thanks a lot! Cheers, Mushtaq ---------------------------- Mushtaq Syed, Ph.D. Principal Digital Signal Processing Engineer Verus Research [cid:image5fd716.JPG@ebfac5a4.47a0da54]<http://> Direct 505-396-7109 Cell 408-514-7821 6100 Uptown Blvd NE, Suite 260 Albuquerque, New Mexico 87110 verusresearch.net ---------------------------- NOTICE: This electronic mail message is intended exclusively for the individual or entity to which it is addressed. This message, together with any attachment, may contain sensitive or privileged information. Any unauthorized review, use, printing, retention, copying, disclosure, or distribution of said email is strictly prohibited. If you have received this message in error, please (1) immediately advise the sender by reply email message and (2) delete all copies of this message

2 3

Quadmath.h not found for float128 arm64 rocky linux
by David Frank 25 Aug '23

25 Aug '23

When compile with boost float128 on arm64 rocky linux, i got a failure of missing quadmath.h Thanks.

3 2

[Compiler] Boost compatibility in a untested compiler version
by Kankanamge, Gimhani 17 Aug '23

17 Aug '23

Hi team, Based on release notes for boost 1.83.0, there is a list of tested compilers (https://www.boost.org/users/history/version_1_83_0.html) But, we are going to use boost 1.83.0 in a different compiler which is not listed here(GCC 8.5.0). In such a case, what is the approach we should use to verify that boost is compatible in our given platform? Thank you. Gimhani Uthpala ------------------------------------------------------------------------------------------------------------ Please read these warnings and restrictions: This e-mail transmission is strictly confidential and intended solely for the ordinary user of the e-mail address to which it was addressed. It may contain legally privileged and/or CONFIDENTIAL information. The unauthorised use, disclosure, distribution and/or copying of this e-mail or any information it contains is prohibited and could, in certain circumstances, constitute a criminal offence. If you have received this e-mail in error or are not an intended recipient please inform London Stock Exchange Group (“LSEG”) immediately by return e-mail or telephone 020 7797 1000. LSEG may collect, process and retain your personal information for its business purposes. For more information please see our Privacy Policy. We advise that in keeping with good computing practice the recipient of this e-mail should ensure that it is virus free. We do not accept responsibility for any virus that may be transferred by way of this e-mail. E-mail may be susceptible to data corruption, interception and unauthorised amendment, and we do not accept liability for any such corruption, interception or amendment or any consequences thereof. Calls to London Stock Exchange Group may be recorded to enable LSEG to carry out its regulatory responsibilities. For more details on the LSEG group of companies click here London Stock Exchange Group plc 10 Paternoster Square London EC4M 7LS Registered in England and Wales No 05369106 ------------------------------------------------------------------------------------------------------------

2 1

JSON and no-alloc
by Marc Oscar Singer 14 Aug '23

14 Aug '23

Greetings, I'm targeting the boost JSON library for an embedded target. There appears to be one place where there could be either a beneficial new feature, or the feature exists and I'm not seeing it. The section about Avoiding Dynamic Allocation is close to what we'd like to see, except that we don't want to depend on a stack buffer for value data. All of the text of the JSON message is present in the string view. It would be desirable to reference the values from there. Let me be a little more explicit. We receive a message in JSON format. The whole of this message must be received before we can pass it to the JSON parser. It's /possible/ to let the JSON parser manage the message as it arrives and manage both the parse and storage of the content. Doing so would require shifting some responsibilities within the firmware that are difficult to change. We parse out the fields we care about and then want to hold onto these values for some time without retaining the memory necessary for the parse itself. Since all of the values and keys are present in the original source buffer passed to parse() as a string_view, we could simply save the string_views for the values and discard the JSON parser. Except, this parser copies the value to another buffer s.t. discarding the parser invalidates the value string_views. Alternatively, if the values themselves were returned as string_views into the source buffer, these string_views would (could) survive destruction of the parser. If we are missing the method by which this can be implemented with the current parser, we'd be delighted to hear it. Cheers -- /Marc Oscar Singer/ *Woollysoft* +1.206.328.1718

3 4

Abwesenheitsnachricht: JSON and no-alloc
by Sören Textor 14 Aug '23

14 Aug '23

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

Full-Text Search is LIVE!
by Vinnie Falco 10 Jul '23

10 Jul '23

Greetings. I am proud to announce that Mohammad’s excellent work on implementing a full-text search which looks into all the Boost libraries and their documentation is now complete, and has been published to the live website. You can access the search by pressing the Search button in the top right of the page: https://boost.org Please note that this is only the first iteration of this search tool and as such it will probably not give the perfect results that everyone expects every time. But now that we have something in place we can feedback, brainstorm on how to make it better, and iterate on it so that it evolves into something that consistently enhances the Boost user experience. To report problems or suggestions related to the search including the user interface, and the indexed contents, please open an issue in the Boost website repository: https://github.com/boostorg/website/issues There is also a “Report Issue” button in the search UI. Thanks!

1 0

[Boost.TypeErasure] - Issue compiling under Windows with Embarcadero C++ Builder 11.3
by Andy Bell 07 Jul '23

07 Jul '23

Hi I'm using the type erasure library but have an issue (which I can workaround) when compiling in Windows 10 using Embarcadero C++ Builder 11.3. My problem is that C++ Builder brings in the Windows SDK Windows.h include file in every Windows VCL UI project it creates *before* any of my code has compiled and it's causing conflicts in boost header member11.hpp. This code is enough to cause the error: #include <boost/type_erasure/any.hpp> #include <boost/type_erasure/any_cast.hpp> #include <boost/type_erasure/builtin.hpp> #include <boost/type_erasure/operators.hpp> #include <boost/type_erasure/member.hpp> #include <boost/type_erasure/free.hpp> #include <boost/mpl/vector.hpp> namespace mynamespace { BOOST_TYPE_ERASURE_MEMBER(ReadStatus) } The error is because Windows.h defines 'interface' but this code from member11.hpp also uses 'interface': template<class P, template<class ...> class interface, class Sig, class Concept, class Base, class ID> using choose_member_interface = typename ::boost::mpl::if_c< ::boost::is_reference::value, typename ::boost::mpl::if_c< ::boost::type_erasure::detail::is_non_const_ref::value, interface<Sig, Concept, Base, const ID>, Base >::type, interface<Sig, Concept, Base, ID> >::type; and the compiler complains of conflicts. Embarcadero support have told me that I can't prevent Windows.h being included in my project before my boost-using code is compiled and attempts I've made to circumvent the problem, such as adding these lines to codegear.hpp: #ifdef interface #undef interface #endif don't work because C++ Builder is still including Windows.h before my code is compiled. To get around the problem, I changed member11.hpp in my boost installation to template<class P, template<class ...> class interface_, class Sig, class Concept, class Base, class ID> using choose_member_interface = typename ::boost::mpl::if_c< ::boost::is_reference::value, typename ::boost::mpl::if_c< ::boost::type_erasure::detail::is_non_const_ref::value, interface_<Sig, Concept, Base, const ID>, Base >::type, interface_<Sig, Concept, Base, ID> >::type; which I don't think will have side effects as 'interface/interface_' here is self-contained, but it doesn't feel like a good long term solution. Embarcadero support said: "Boost brings windows.h in because boost pulls it, *IF* the application is compiled for multi-threading then boost needs to access the OS threading functions, this is when you compile *without* the VCL." and I have confirmed this by creating a simple, multi-threaded Windows console application in C++ Builder... My question is: Is there a better way to work around this issue? My tests indicate that the Type Erasure library is working properly with my change, but it feels more like a hack than a fix... Thanks, Andy Bell Control Systems & Software Engineer Tel: +44 (0)1903 891700 Fax: +44 (0)1903 893888 Web: www.thermcosystems.com<http://www.thermcosystems.com/> www.csd-epi.com<http://www.csd-epi.com/> [cid:image002.png@01D9ADAA.693C8600] [Logo, company name Description automatically generated] P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the intended recipient. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Tetreon Technologies Limited. Warning: Although Tetreon Technologies Limited has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. Tetreon Technologies Ltd is a limited company registered in England and Wales. Company Registration No. 4966845 Registered Offices: Highfield, Rock Road, Washington, West Sussex, RH20 3BH, England

2 1

[asio] monitoring io_context load
by Dmitry 07 Jul '23

07 Jul '23

Hello, I would like to have a metric that measures time spent for work (executing completion handlers) vs time spent waiting for work in thread pool executing io_context::run(). It will help to estimate service capacity (i.e. how many more requests per second it can handle). It is similar to the system's CPU usage metric but CPU usage metric does not include waiting for mutex locks or sync io performed from completion handlers. In our performance tests io_context becomes overloaded (the queue grows faster than it's processed) when CPU usage is about 85%. I would like to have a metric that shows 100% in this case. There is BOOST_ASIO_CUSTOM_HANDLER_TRACKING macro that allows to intercept handler invocations and to measure execution time. But in the case of many lightweight handlers measuring time can bring significant overhead. I'm considering adding similar macros before and after waiting for the condition variable and epoll to measure wait time and then calculate execution time. I'm writing to ask if there is a better alternative? If not, would you be interested in a patch that adds "Handler Tracking" macros around wait calls? Thank you, Dmitry

3 6

Please remove me from this list
by Vitaly Budovski 03 Jul '23

03 Jul '23

The web and email unsubscribe methods do not seem to work.

1 0

[python][shared_ptr_from_python.hpp] looks like copy/paste or merge error
by Ran Regev 29 Jun '23

29 Jun '23

Hi, The code in construct() seems to surfer from copy/paste or merge error. It seems as though the following lines are duplicated in the else clause: void *const storage = ((converter::rvalue_from_python_storage<SP<T> >*)data)->storage.bytes; // Deal with the "None" case. if (data->convertible == source) new (storage) SP<T>(); Please take a look at: https://www.boost.org/doc/libs/1_82_0/boost/python/converter/shared_ptr_fro… Ran.

1 0

[multiprecision] why 128 bit numbers isn't used in msvc?
by shar yashuv Giat 29 Jun '23

29 Jun '23

msvc added 128 bit numbers(in the header __msvc_int128.hpp). I know multiprecision uses __128 to improve performance so why doesn't it use msvc version? it's seems easy to change and will probably improve performance.

2 1

assign a large integer to a cpp_int
by Matthew Mawson 27 May '23

27 May '23

I want to assign a large number to a cpp_int variable like this: cpp_int large = 30414093201713378043612608166064768844377641568960512000000000000; and I get this: error: integer literal is too large to be represented in any integer type. Thanks!

2 1

Abwesenheitsnachricht: assign a large integer to a cpp_int
by Sören Textor 27 May '23

27 May '23

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

[boost::locale::generator] Calling boost::locale::generator results in an exception in EnterCriticalSection
by M L 24 May '23

24 May '23

Hello, calling boost::locale::generator results in an exception in EnterCriticalSection. Does anybody have a hint to the cause of this problem? Every small clue is welcome. What could be a possible workaround? What is usually the reason for an exception in EnterCriticalSection? Code snippet: boost::locale::generator generator; generator.add_messages_path("..."); generator.add_messages_domain(".."); std::string lngCode = "en"; std::locale = generator(lngCode + ".WINDOWS-1252"); // this line crashes -> 0x0000005 EnterCriticalSection Boost Version: (boost_1_60_0) Visual Studio 2013 Some more hints: - it seems that there is a problem reading the translation file, which works fine in other applications. - there are no threads in the code - the problem is project dependent. Same code works in a different project. - the problem only appears if a specific header is included, but nothing in this header is ever executed before the crash. Removing the header/cpp removes the problem. - some C code is present in the code - the problem even appears when moving the snipped in main. Thanks for help.

2 1

Boost ASIO: Problems building a conditional variable using io_context / strand
by Suraaj K S 23 May '23

23 May '23

Hi all, In boost-asio, I realized that there was no easy way to have something that resembles a condition variable. However, I realized that I could get something very similar using stackful coroutines ( https://www.boost.org/doc/libs/1_66_0/doc/html/boost_asio/overview/core/spa…) while using an io_context as a 'queue' for completion tokens. Below is my approach: *#include "asio_types.hpp"#include <atomic>#include <iostream>class async_pending_queue {public: async_pending_queue() : pending_handlers_(0), strand_(pending_queue_), wg_(asio::make_work_guard(pending_queue_)) {} template <typename CompletionToken> auto async_submit( CompletionToken &&token, std::function<void(void)> atomic_action = [] {}) { auto init = [this, &atomic_action](auto completion_handler) { auto posted_lambda = [handler = std::move(completion_handler), this]() mutable { pending_handlers_--; asio_sys_err ec; handler(ec); }; post(strand_,std::move(posted_lambda)); pending_handlers_++; atomic_action(); }; return asio::async_initiate<CompletionToken, void(asio_sys_err)>(init, token); } int pending_count() { return pending_handlers_.load(); } // It may not run 1 and run 0 bool try_run_one() { auto cnt = pending_queue_.poll_one(); std::cout << "completion token result" << cnt << std::endl; bool ret = (cnt == 1); return ret; }private: std::atomic<unsigned int> pending_handlers_; asio_ioctx pending_queue_; asio_ioctx::strand strand_; decltype(asio::make_work_guard(pending_queue_)) wg_;};* Here, one simply uses calls `my_async_pending_queue.async_submit(yield)`, if calling from a stackful coroutine. The coroutine can be continued by calling `my_async_pending_queue.try_run_one()`. Using this, I wanted to build a 'memory checker'. It has two functions -> `request_space` and `free_space`. A coroutine calls `request_space`, which may block if there is no space left. Meanwhile, another thread / coroutine can call `free_space`, which will run blocked coroutines if possible. I built a toy memory checker wrapper as follows: *#ifndef MEM_CHECK_HPP#define MEM_CHECK_HPP#include <cstddef>#include <mutex>#include <queue>#include <boost/asio.hpp>#include <boost/asio/spawn.hpp>namespace asio = boost::asio;using asio_ioctx = asio::io_context;using asio_sys_err = boost::system::error_code;using asio::yield_context;#include "async_pending_queue.hpp"class MemoryChecker {public: using bytes_cnt = size_t; MemoryChecker(asio_ioctx &ioctx, bytes_cnt total_mem = 1024, bytes_cnt initial_fill = 0); // This requests some space, and possibly yields; void request_space(bytes_cnt cnt, yield_context yield); void free_space(bytes_cnt cnt);private: bytes_cnt get_available_mem(); const bytes_cnt total_mem_; bytes_cnt mem_used_; std::queue<bytes_cnt> request_queue_; async_pending_queue request_routines_; std::mutex lock_; asio_ioctx::strand fifo_strand_; asio_ioctx &completion_ioctx_;};inline MemoryChecker::MemoryChecker(asio_ioctx &ioctx, bytes_cnt total_mem, bytes_cnt initial_fill) : total_mem_(total_mem), mem_used_(initial_fill), request_queue_{}, lock_{}, request_routines_{}, completion_ioctx_(ioctx), fifo_strand_(ioctx) {}inline MemoryChecker::bytes_cnt MemoryChecker::get_available_mem() { assert(total_mem_ >= mem_used_); return total_mem_ - mem_used_;}inline void MemoryChecker::request_space(bytes_cnt cnt, yield_context yield) { // if (cnt > total_mem_) throw logic_error lock_.lock(); assert(cnt <= total_mem_); assert(cnt > 0); if (request_queue_.empty()) { assert(request_routines_.pending_count() == 0); if (get_available_mem() >= cnt) { // We bypass the pending queue mem_used_ += cnt; lock_.unlock(); return; } } assert(request_queue_.size() == request_routines_.pending_count()); std::cout << "Pushing " << cnt << std::endl; request_queue_.push(cnt); auto wg = asio::make_work_guard(completion_ioctx_); request_routines_.async_submit(yield, [this] { lock_.unlock(); }); auto oldest_req{request_queue_.front()}; assert(cnt == oldest_req); request_queue_.pop(); mem_used_ += cnt; assert(request_queue_.size() == request_routines_.pending_count()); asio::post(fifo_strand_, yield);}inline void MemoryChecker::free_space(bytes_cnt cnt) { { std::lock_guard<std::mutex> lg{lock_}; mem_used_ -= cnt; // Here, we own the lock, and free as many coroutines as we can while (true) { if (request_queue_.size() == 0) { std::cout << "No pending requests. Bailing" << std::endl; break; } assert(request_queue_.size() == request_routines_.pending_count()); auto oldest_req{request_queue_.front()}; auto available_mem{get_available_mem()}; if (available_mem < oldest_req) { std::cout << "Oldest request is larger than available_mem. Bailing" << std::endl; break; } assert(request_routines_.try_run_one() == true); } }}#endif /* MEM_CHECK_HPP */* Here is a test program that can run it: *#include "mem_check.hpp"#include <thread>#include <unistd.h>constexpr size_t mc_size{4};asio_ioctx ioctx;size_t total{0};MemoryChecker mc{ioctx, mc_size};void requestor_coroutine(size_t rq,yield_context yield) { asio::steady_timer t(ioctx); while (true) { total += rq; mc.request_space(rq, yield); std::cout << "Got requested space "; asio_sys_err ec; }}int main() { asio::spawn(ioctx, [](yield_context yield) { requestor_coroutine(1,yield); }); asio::spawn(ioctx, [](yield_context yield) { requestor_coroutine(2,yield); }); asio::spawn(ioctx, [](yield_context yield) { requestor_coroutine(3,yield); }); asio::spawn(ioctx, [](yield_context yield) { requestor_coroutine(4,yield); }); std::thread t([] { ioctx.run(); }); while (true) { getchar(); std::cout << total << std::endl; if (total > 0) { std::cout << "freeing" << std::endl; mc.free_space(1); total -= 1; } } t.join();}* Finally, the problem we face is as follows. When we run the program, the assertion `total_mem >= mem_used_` fails. On some further investigation, I realized that our completion token was being called even when we do not call `try_run_one`, which was very weird. Finally, somewhat more surprisingly, If I replace *post(stand_,std::move(posted_lambda));* by *post(pending_queue_,std::move(posted_lambda));*, things seem to work. However, the asio documentation says that only strands guarantee a FIFO execution order. I am not sure if using a simple `io_context` will work as a FIFO queue (even though it seems to in these examples). Any inputs would be helpful - I am happy to hear the problem in this implementation, as well as other implementations (for example, using a std::queue as a proper queue instead of this io_context hack). This question has also been posted here: https://stackoverflow.com/questions/76310252/c-boost-asio-building-a-condit… . Thanks, Suraaj

3 2

Re: [Boost-users] New Website !
by Vinnie Falco 11 May '23

11 May '23

On Thu, May 11, 2023 at 8:08 AM Damien via Boost-users <boost-users(a)lists.boost.org> wrote: > This looks really good. Congratulations to the team. Thank you very much for the kind words! Regards

1 0

Re: [Boost-users] New Website !
by Damien 11 May '23

11 May '23

This looks really good. Congratulations to the team. Damien

1 0

New Website !
by Vinnie Falco 11 May '23

11 May '23

Hey, it’s Vinnie here again! I have some very exciting news to share with you. The renovated website for Boost that we’ve been working on for far too long is now going into its Public Beta phase! Feel free to poke around and kick the tires but keep in mind this is a piece of software and it is still under development. Some parts are missing, incomplete,or buggy. Without further ado: https://boost.revsys.dev This public beta will extend for at least 10 weeks as we finish the last remaining features, and put a few more rounds of polish on the artwork, visual styling, and user interface. After that if you like what you see then we will reset the database, move the repositories and the site to their new homes, and then deploy it for real! If you have suggestions or wish to report problems please feel welcome to open an issue here: https://github.com/cppalliance/temp-site/issues This is a Django site written and maintained in Python by a great group of folks from https://www.revsys.com/. The project is coordinated by Frank Wiles (https://www.revsys.com/about/bio/frankwiles) who shares the same deep commitment to open source that we Boost people do. We chose Django because it is well understood and supported, and because Python composes well with ease of maintenance. This technology stack allows us to execute on our future plans with confidence. Some cool things about this website include: * Log in with GitHub or Google * Light and Dark themes with selector * Asciidoc markdown for dynamic content * Antora content sources for site documentation * Data-driven dynamic pages for libraries and releases * Integrated control panel for producing Boost releases * Full-text search across the documentation and library headers * Professionally designed logo to evoke identity and instant recognition The layout of the site is carefully thought out to make sure that information can be found quickly. Fundamental topics each get a dedicated word in the top level navigation, visible on every page including the site and library documentation. Most of the information which is not library-specific is warehoused in “site docs” which is a collection of individual Antora content sources each authored in Asciidoc. Anyone can update the information on the website simply by contributing to the site-docs via pull request: https://github.com/cppalliance/site-docs Antora and Asciidoc are potent technologies that offer Boost plenty of room to grow to make our site documentation and library documentation more effective for users. While the initial release of the website after the beta will only have the basic functionality, we have many future plans. Some of these you have heard about already and some are new: * A web-based forum which interacts seamlessly with the mailing list * Polls and surveys for measuring the sentiment of Boost users and stakeholders * News section for aggregating off-site links, blog posts, and release progress messages * Integrated Review process. Outcomes go in the database and become dynamic content. * User Profiles record and show activity such as review participation or library submission We’re all very excited and proud of the work that went into this thing and hope that it really fulfills the positive impact that we intended. Thanks! Vinnie

1 0

b2 error in nvidia enviroment
by Cho-Kuen Ng 26 Apr '23

26 Apr '23

I tried to build under nvidia environment and got the following b2 error: ../boost_1_73_0/tools/build/share/boost-build/src/build/toolset.jam:44: in toolset.using ERROR: rule "nvc.init" unknown in module "toolset". I put the following line in the site-config file using nvc : : CC ; What compiler toolset should I use under nvidia? Thanks.

1 0

Re: [Boost-users] errors in multiprecision
by John Maddock 21 Apr '23

21 Apr '23

On 20/04/2023 18:28, Gero Peterhoff via Boost-users wrote: > Am 20.04.23 um 18:38 schrieb John Maddock via Boost-users: >> On 20/04/2023 16:58, Gero Peterhoff via Boost-users wrote: >>> Hi John, >>> some functions do not work with multiprecision-integer-types, e.g. >>> >>> using T = boost::multiprecision::int256_t; >>> using ::std::isinf; >>> >>> const auto x = T{5}; >>> const auto y = isinf(x); // ct error >>> std::cout << y << std::endl; >>> >>> gives a CT error. >>> >> Correct. Those functions are pretty meaningless in the context of >> integer types, and no one has ever asked for them. >> >> John. > > > Ok, herewith I ask for it then :-) Finally this is relevant in the > template context or a functions with std- AND multiprecision-types > should/must work. I'll add it to the list, but be aware that this is not always supported for regular integer types: https://godbolt.org/#g:!((g:!((g:!((h:codeEditor,i:(filename:'1',fontScale:14,fontUsePx:'0',j:1,lang:c%2B%2B,selection:(endColumn:2,endLineNumber:6,positionColumn:2,positionLineNumber:6,selectionStartColumn:2,selectionStartLineNumber:6,startColumn:2,startLineNumber:6),source:'%23include+%3Ccmath%3E%0A%0Aint+main(int+argc)%0A%7B%0A++++return+std::isinf(argc)%3B%0A%7D%0A'),l:'5',n:'0',o:'C%2B%2B+source+%231',t:'0')),k:33.333333333333336,l:'4',n:'0',o:'',s:0,t:'0'),(g:!((h:compiler,i:(compiler:vcpp_v19_33_x64,deviceViewOpen:'1',filters:(b:'0',binary:'0',binaryObject:'1',commentOnly:'0',demangle:'0',directives:'0',execute:'0',intel:'0',libraryCode:'0',trim:'1'),flagsViewOpen:'1',fontScale:15,fontUsePx:'0',j:1,lang:c%2B%2B,libs:!(),options:'-O2',selection:(endColumn:1,endLineNumber:1,positionColumn:1,positionLineNumber:1,selectionStartColumn:1,selectionStartLineNumber:1,startColumn:1,startLineNumber:1),source:1),l:'5',n:'0',o:'+x64+msvc+v19.33+(Editor+%231)',t:'0')),k:33.333333333333336,l:'4',n:'0',o:'',s:0,t:'0'),(g:!((h:output,i:(compilerName:'x64+msvc+v19.latest',editorid:1,fontScale:14,fontUsePx:'0',j:1,wrap:'1'),l:'5',n:'0',o:'Output+of+x64+msvc+v19.33+(Compiler+%231)',t:'0')),k:33.33333333333333,l:'4',n:'0',o:'',s:0,t:'0')),l:'2',n:'0',o:'',t:'0')),version:4 John.

1 0

Re: [Boost-users] errors in multiprecision
by Gero Peterhoff 20 Apr '23

20 Apr '23

Am 20.04.23 um 18:38 schrieb John Maddock via Boost-users: > On 20/04/2023 16:58, Gero Peterhoff via Boost-users wrote: >> Hi John, >> some functions do not work with multiprecision-integer-types, e.g. >> >> using T = boost::multiprecision::int256_t; >> using ::std::isinf; >> >> const auto x = T{5}; >> const auto y = isinf(x); // ct error >> std::cout << y << std::endl; >> >> gives a CT error. >> > Correct. Those functions are pretty meaningless in the context of integer types, and no one has ever asked for them. > > John. Ok, herewith I ask for it then :-) Finally this is relevant in the template context or a functions with std- AND multiprecision-types should/must work. thx Gero

1 0

Re: [Boost-users] errors in multiprecision
by John Maddock 20 Apr '23

20 Apr '23

On 20/04/2023 16:58, Gero Peterhoff via Boost-users wrote: > Hi John, > some functions do not work with multiprecision-integer-types, e.g. > > using T = boost::multiprecision::int256_t; > using ::std::isinf; > > const auto x = T{5}; > const auto y = isinf(x); // ct error > std::cout << y << std::endl; > > gives a CT error. > Correct. Those functions are pretty meaningless in the context of integer types, and no one has ever asked for them. John.

1 0

errors in multiprecision
by Gero Peterhoff 20 Apr '23

20 Apr '23

Hi John, some functions do not work with multiprecision-integer-types, e.g. using T = boost::multiprecision::int256_t; using ::std::isinf; const auto x = T{5}; const auto y = isinf(x); // ct error std::cout << y << std::endl; gives a CT error. cu Gero

1 0

Re: [Boost-users] Much slower compilation time with boost-1.81 than boost-1.80 + much bigger .text section
by Niall Douglas 18 Apr '23

18 Apr '23

On 17/04/2023 14:33, Dominique Pellé via Boost-users wrote: > Hi > > 1) Compiling the attached "brands.cpp" file which uses > boost::container::flat_set is very slow with clang when using > boost-1.81.0. It was much faster with boost-1.80.0 somehow. Thanks for reporting this. Peter Dimov looked into this and found that the cause is recently added use of __forceinline. A suitable workaround until the next Boost release is -DBOOST_CONTAINER_DISABLE_FORCEINLINE I can't speak for Ion, but I'd assume it'll be fixed next Boost release. Once again thanks for reporting this, it wasn't noticed by the usual release testing. Niall

1 0

Much slower compilation time with boost-1.81 than boost-1.80 + much bigger .text section
by Dominique Pellé 18 Apr '23

18 Apr '23

Hi 1) Compiling the attached "brands.cpp" file which uses boost::container::flat_set is very slow with clang when using boost-1.81.0. It was much faster with boost-1.80.0 somehow. 2) Furthermore, the size of the .text section is much bigger when using boost-1.81.0 than with boost-1.80.0 when using clang. The source file is a simplification of an actual file in my project. Note that the code is in anonymous namespace (removing the anonymous namespace makes the compilation time much faster, presumably because there are more optimizations in the anonymous namespace). Benchmarks with clang-16 + boost-1.81.0 (on Linux Ubuntu-22.04): ``` $ time clang++-16 -isystem boost-1.81 -O2 -DNDEBUG \ -std=c++14 -o brands.o -c brands.cpp real 1m46.638s user 1m46.090s sys 0m0.520s $ size brands.o text data bss dec hex filename 2403932 20032 48 2424012 24fccc brands.o ``` Compare with the older boost-1.80.0: ``` $ time clang++-16 -isystem boost-1.80 -O2 -DNDEBUG \ -std=c++14 -o brands.o -c brands.cpp real 0m2.163s user 0m2.122s sys 0m0.041s $ size brands.o text data bss dec hex filename 101280 20032 48 121360 1da10 brands.o ``` In other words: - file is 81 times slower to compile with boost-1.81 than with boost-1.80 - the .text section is 23 times bigger with boost-1.81 than with boost-1.80 This may be a clang compiler issue, but since the performance regression is introduced from boost-1.80.0 to boost-1.81.0 I'm, reporting it here (I may report it to clang later depending on how the discussion here goes). It's even worse with older clang compilers. The table below shows the compilation time of brands.cpp file and size of the .text section for with various compilers using boost-1.80 and boost-1.81: ``` compiler boost compilation time size .text section -------- ----- ---------------- ------------------ clang-16 1.81 106.638 sec 2,403,932 bytes clang-16 1.80 2.164 sec 101,280 bytes clang-15 1.81 137.508 sec 2,861,332 bytes clang-15 1.80 2.527 sec 107,944 bytes clang-14 1.81 153.504 sec 3,033,487 bytes clang-14 1.80 2.294 sec 111,599 bytes clang-5.0 1.81 276.031 sec 2,720,187 bytes clang-5.0 1.80 2.328 sec 126,811 bytes gcc-12.1 1.81 2.821 sec 139,833 bytes gcc-12.1 1.80 2.505 sec 140,217 bytes gcc-7.5 1.81 1.943 sec 121,497 bytes gcc-7.5 1.80 1.707 sec 122,050 bytes ``` Regards Dominique PS: full versions of compiler used in above table (--version option): - Ubuntu clang version 16.0.2 (++20230414073413+b5aa566a7e53-1~exp1~20230414073428.73) - Ubuntu clang version 15.0.7 - Ubuntu clang version 14.0.0-1ubuntu1 - clang version 5.0.2 (tags/RELEASE_502/final) - gcc-12 (Ubuntu 12.1.0-2ubuntu1~22.04) 12.1.0 - gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0

1 1

Re: [Boost-users] Boost configuration errors and problems
by Gavin Lambert 17 Apr '23

17 Apr '23

On 18/04/2023 02:32, Klebsch, Mario via wrote: > Since the vast majority of boost are header-only libraries, my usual > advice is no NOT use precompiled libraries of boost but to use boost > as a kind of source code library. This way, the source code is always > compiled with the same compiler flags as the rest of your code. > > I usually have to include > .../libs/system/src/error_code.cpp > .../libs/thread/src/pthread/* (or .../libs/thread/src/win32/*) > .../libs/chrono/src/* > .../libs/filesystem/src/* > In my Makefile, CMakeLists.txt or .vxcproj. Note that while doing this sort of thing is a valid strategy for a single application, it will get you into trouble if you split your app into separate EXE and DLL files and want to have any Boost types in the interfaces between them.

1 0

Re: [Boost-users] Boost configuration errors and problems
by Klebsch, Mario 17 Apr '23

17 Apr '23

Hello, > No suitable build variant has been found. > The following variants have been tried and rejected: > * boost_filesystem.lib (shared, Boost_USE_STATIC_LIBS=ON) Since the vast majority of boost are header-only libraries, my usual advice is no NOT use precompiled libraries of boost but to use boost as a kind of source code library. This way, the source code is always compiled with the same compiler flags as the rest of your code. I usually have to include .../libs/system/src/error_code.cpp .../libs/thread/src/pthread/* (or .../libs/thread/src/win32/*) .../libs/chrono/src/* .../libs/filesystem/src/* In my Makefile, CMakeLists.txt or .vxcproj. On Windows I also have to #define BOOST_ALL_NO_LIB to prevent the magic from trying to pick up pre-built libraries at link time and sometimes BOOST_THREAD_BUILD_LIB or BOOST_ALL_STATIC_LINK are required. Klebsch Mario Funktion | R&D Tel: +49 (0) 531 38 701 718 Raum: Braunschweig, E20 Diese E-Mail und die an sie angehängten Dateien sind ausschließlich für Personen oder Institutionen bestimmt, deren Namen oben aufgeführt sind. Sie können Informationen enthalten, die durch das Berufsgeheimnis geschützt sind und deren Weitergabe strengstens untersagt ist. Jede elektronische Nachricht kann geändert werden. ACTIA lehnt jede Verantwortung für diese Nachricht ab. Der Inhalt dieser Nachricht stellt keine Verpflichtung seitens unseres Unternehmens dar. Wenn Sie kein Empfänger sind, weisen wir Sie darauf hin, dass das Lesen, Vervielfältigen oder Verteilen strengstens untersagt ist. Wir bitten Sie daher, uns umgehend über diesen Brief zu informieren und diese Nachricht sowie eventuell beigefügte Unterlagen aus Ihrem Postfach zu löschen. Danke. This e-mail and the files attached to it are intended exclusively for persons or institutions whose names are listed above. They may contain information that is protected by professional secrecy and the disclosure of which is strictly prohibited. Any electronic message can be modified. ACTIA declines all responsibility for this message. The content of this message does not represent a commitment on the part of our company. If you are not a recipient, we would like to point out that reading, copying or distribution is strictly prohibited. We therefore ask you to inform us immediately about this letter and to delete this message and any accompanying documents from your mailbox. Thank you.

1 0

Re: [Boost-users] Precompiled Windows ARM/ARM64 binaries
by Tom Kent 14 Apr '23

14 Apr '23

On Fri, Apr 14, 2023 at 12:39 PM Stephan Brunner via Boost-users < boost-users(a)lists.boost.org> wrote: > Hi, > > are there any plans to ship precompiled windows binaries for ARM and/or > ARM64 at some time on SourceForge [1]? > Currently only a x86 and a x64 build is available there. > If not, I'll look into building my own version for those architectures. > > Thanks a lot! > > [1] https://sourceforge.net/projects/boost/files/boost-binaries/1.81.0/ > > No, I don't have a good windows arm/arm64 machine to test on, so don't want to make binaries I can't at least run a smoke test on. Beyond that, it would make the build process a lot more complex to run on multiple machines. The nice thing about i368 and amd64 is that you can run them both on the same windows install! Tom

1 0