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

Is there any official documentation on shutdown procedure for ASIO SSL socket?
by Ivan Matek 11 Oct '22

11 Oct '22

There is this SO answer https://stackoverflow.com/a/25703699/ with Vinnie comment from 8y ago that it should be added to documentation. :) I can not find anything in the documentation so I presume the documentation/example does not exist, but I decided to double check. regards, Ivan

3 2

Very slow destructors of binary_oarchive and filtering_streambuf
by boost.5nyej＠simplelogin.com 03 Oct '22

03 Oct '22

Hello, I just posted a question on StackOverflow, but I realised that this mailing list might be a better place. The link to the question is: https://stackoverflow.com/questions/73938656/very-slow-destructors-of-binar… Tl;dr; I have a code that serializes a big object by using binary_oarchive and filtering_bufstream. The writing on its own takes around 28 minutes, but the deconstructors of the mentioned classes take 37 and 36 minutes, respectively. It is very strange to me that they would take so much time to run, as the first deconstructor adds only 2KiB of data, and the second deconstructor doesn't change anything. Could you help me find the root cause of those execution times?

1 0

[serialisation] Strange "direct access" warning on OSX for basic_text_oprimitive
by Marco Craveiro 29 Sep '22

29 Sep '22

Hi Boost Users, First, a great thanks to the authors of the boost serialisation library, which I have used successfully across projects and has proven invaluable. Now to my problem. I have been investigating for a little while a strange warning I get when linking on OSX; the results of my investigation can be found here [1]. The TL; DR of it is as follows: my OSX debug build has a warning (indented for ease of reading): ld: warning: direct access in function 'boost::archive::basic_text_oprimitive< std::__1::basic_ostream<char, std::__1::char_traits<char> > >::~basic_text_oprimitive()' from file 'vcpkg_installed/x64-osx/debug/lib/libboost_serialization.a(basic_text_oprimitive.o)' to global weak symbol 'std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::endl<char, std::__1::char_traits<char> > (std::__1::basic_ostream<char, std::__1::char_traits<char> >&)' This warning is caused by a mismatch in visibility settings between my project and vcpkg's build of boost. However, as far as I can see, both projects are using "-fvisibility=default", meaning there should be no mismatch. Also, no other warnings show up but if I change the project settings I then get hundreds of warnings (again, for details see ticket). What I find even more puzzling is that I am using all three types of archives (Text, XML and Binary). Of these three, only Text produces this warning. As the problem is with the destructors, I did a quick inventory of the destructors to see how they differ: basic_xml_oarchive.hpp: [2] BOOST_ARCHIVE_OR_WARCHIVE_DECL ~basic_xml_oarchive() BOOST_OVERRIDE; basic_text_oarchive.hpp: [3] ~basic_text_oarchive() BOOST_OVERRIDE {} basic_binary_oarchive.hpp: [4] no destructor. So my question is, should text archive also have a BOOST_ARCHIVE_OR_WARCHIVE_DECL macro, and would that fix my warning? If so I can submit a PR. Many thanks for your time. Marco [1] https://github.com/Microsoft/vcpkg/issues/4497 [2] https://github.com/boostorg/serialization/blob/develop/include/boost/archiv… [3] https://github.com/boostorg/serialization/blob/develop/include/boost/archiv… [4] https://github.com/boostorg/serialization/blob/develop/include/boost/archiv… -- Marco Craveiro MD, Domain Driven Consulting blog: https://mcraveiro.github.io/index.html twitter: https://twitter.com/MarcoCraveiro That the Ideas are themselves manifestations (of the Idea-Idea) and that the Idea-Idea is a-kind-of Manifestation-Idea—which is a-kind-of itself, so that the system is completely self-describing— would have been appreciated by Plato as an extremely practical joke [Plato]. -- Alan Key

1 0

Re: [Boost-users] [boost] [signals2][variant] inline warning with MSVC 2022
by Frank Mori Hess 22 Sep '22

22 Sep '22

On Thu, Sep 22, 2022 at 8:57 AM Peter Dimov <pdimov(a)gmail.com> wrote: > > That's complete nonsense. First, Microsoft invented __forceinline, so > making BOOST_FORCEINLINE be a no-op on the very compiler for which > the feature has been added would be ridiculous. Second, it does force > inlining, that's why it's called __forceinline. The whole point of the warning > is to warn about the rare cases where the compiler does not honor the > command; it exists because people want to know whether their "force > inline" orders are ignored. But no boost user wants to be warned about some internal implementation detail of a boost library. So every boost usage of BOOST_FORCEINLINE needs to add a #pragma warning(disable: 4714), awesome! Who is the maintainer of variant anyways? -- Frank

1 0

TSan error with boost::interprocess::message_queue on macOS ARM
by vl01＠jens-carl.de 22 Sep '22

22 Sep '22

Hello List, I'm using the boost::interprocess::message_queue in a project and to verify everything is working I created a test case. In that test case I'm sending and receiving data via threads. The test passes on Linux, Windows with no sanitizer and also with AddressSanitizer and ThreadSanitizer. I recently added Apple Silicon (M1) to the test matrix and now the test run with ThreadSanitizer enabled fails. Is boost::interprocess::message_queue thread-safe? Can the reported TSan error be an false-positive? If it that case, what test can I run to verify that? I looked at code of atomic_cas32() and it uses the legacy built-in __sync_val_compare_and_swap(). Can it be that that built-in isn't supported on ARM? Is there a newer built-in which should be used? The reported TSan error: -- snip ================== WARNING: ThreadSanitizer: data race (pid=4146) Atomic write of size 4 at 0x000104af4028 by thread T2: #0 __tsan_atomic32_compare_exchange_val <null>:81245684 (libclang_rt.tsan_osx_dynamic.dylib:arm64e+0x57854) #1 boost::interprocess::ipcdetail::atomic_cas32(unsigned int volatile*, unsigned int, unsigned int) atomic.hpp:581 (tsan_boost:arm64+0x100005b30) Previous read of size 4 at 0x000104af4028 by thread T1: #0 boost::interprocess::ipcdetail::spin_mutex::try_lock() mutex.hpp:100 (tsan_boost:arm64+0x100006eb0) #1 void boost::interprocess::ipcdetail::try_based_lock<boost::interprocess::ipcdetail::spin_mutex>(boost::interprocess::ipcdetail::spin_mutex&) common_algorithms.hpp:62 (tsan_boost:arm64+0x100006e28) SUMMARY: ThreadSanitizer: data race atomic.hpp:581 in boost::interprocess::ipcdetail::atomic_cas32(unsigned int volatile*, unsigned int, unsigned int) -- snap Here is a code example which demonstrates the test case -- snip #include <boost/interprocess/ipc/message_queue.hpp> #include <iostream> #include <vector> #include <thread> #include <memory> struct MessageQueueImpl { MessageQueueImpl() { boost::interprocess::permissions file_permissions; file_permissions.set_permissions(0660); queue = std::make_unique<boost::interprocess::message_queue>(boost::interprocess::create_only, "tsanqueue", 10, 15, file_permissions); } std::unique_ptr<boost::interprocess::message_queue> queue; }; class MessageQueue { public: MessageQueue() : m_impl(std::make_unique<MessageQueueImpl>()) {} void send(const std::vector<uint8_t>& buffer) { m_impl->queue->send(buffer.data(), buffer.size(), 0); } void receive(std::vector<uint8_t>& buffer) { boost::interprocess::message_queue::size_type received_size = 0; buffer.resize(m_impl->queue->get_max_msg_size()); uint32_t prio; m_impl->queue->receive(buffer.data(), buffer.size(), received_size, prio); buffer.resize(received_size); } private: std::unique_ptr<MessageQueueImpl> m_impl; }; int main() { auto uut = std::make_unique<MessageQueue>(); std::thread sender([&uut]{ for(uint8_t i = 0; i < 3; ++i) { const std::vector<uint8_t> send_buffer = {i}; uut->send(send_buffer); } }); std::thread receiver([&uut]{ for(uint8_t i = 0; i < 3; ++i) { std::vector<uint8_t> receive_buffer; uint32_t prio; uut->receive(receive_buffer); std::cout << "buffer received:\n"; for (const auto i : receive_buffer) { std::cout << i << '\n'; } } }); if(sender.joinable()) { sender.join(); } if(receiver.joinable()) { receiver.join(); } return 0; } -- snap Cheers, Jens

3 3

Re: [Boost-users] [boost] [signals2][variant] inline warning with MSVC 2022
by Frank Mori Hess 22 Sep '22

22 Sep '22

On Wed, Sep 21, 2022 at 12:32 PM Peter Dimov <pdimov(a)gmail.com> wrote: > > That's not very user friendly; maybe the user _wants_ the warning in his code, > and the above would disable it even if no Boost header that uses > BOOST_FORCEINLINE (and generates a warning) has been included. > Okay, then maybe BOOST_FORCEINLINE shouldn't be defined as __force_inline on compilers where it doesn't actually force inlining. If the compiler is just going to treat it as a suggestion, I don't see the point of boost headers using it and then suppressing the warning. -- Frank

1 0

[signals2][variant] inline warning with MSVC 2022
by Gavin Lambert 21 Sep '22

21 Sep '22

This may not be a new issue, as I'm trying to update a project from Boost 1.68 to 1.80 (big jump!), but in trying to compile I'm being hit with this lengthy warning (and this particular project is building with warnings as errors, so this is problematic): warning C4714: function 'class boost::variant<class boost::shared_ptr<void>,class boost::signals2::detail::foreign_void_shared_ptr> __cdecl boost::detail::variant::visitation_impl<struct boost::mpl::int_<0>,struct boost::detail::variant::visitation_impl_step<struct boost::mpl::l_iter<struct boost::mpl::l_item<struct boost::mpl::long_<3>,class boost::weak_ptr<class boost::signals2::detail::trackable_pointee>,struct boost::mpl::l_item<struct boost::mpl::long_<2>,class boost::weak_ptr<void>,struct boost::mpl::l_item<struct boost::mpl::long_<1>,class boost::signals2::detail::foreign_void_weak_ptr,struct boost::mpl::l_end> > > >,struct boost::mpl::l_iter<struct boost::mpl::l_end> >,class boost::detail::variant::invoke_visitor<class boost::signals2::detail::lock_weak_ptr_visitor const ,0>,void const *,struct boost::variant<class boost::weak_ptr<class boost::signals2::detail::trackable_pointee>,class boost::weak_ptr<void>,class boost::signals2::detail::foreign_void_weak_ptr>::has_fallback_type_>(int,int,class boost::detail::variant::invoke_visitor<class boost::signals2::detail::lock_weak_ptr_visitor const ,0> &,void const *,struct boost::mpl::bool_<0>,struct boost::variant<class boost::weak_ptr<class boost::signals2::detail::trackable_pointee>,class boost::weak_ptr<void>,class boost::signals2::detail::foreign_void_weak_ptr>::has_fallback_type_,struct boost::mpl::int_<0> *,struct boost::detail::variant::visitation_impl_step<struct boost::mpl::l_iter<struct boost::mpl::l_item<struct boost::mpl::long_<3>,class boost::weak_ptr<class boost::signals2::detail::trackable_pointee>,struct boost::mpl::l_item<struct boost::mpl::long_<2>,class boost::weak_ptr<void>,struct boost::mpl::l_item<struct boost::mpl::long_<1>,class boost::signals2::detail::foreign_void_weak_ptr,struct boost::mpl::l_end> > > >,struct boost::mpl::l_iter<struct boost::mpl::l_end> > *)' marked as __forceinline not inlined I'm not sure whether the Real Bug™ is in signals2 or in variant, but I don't think it's in any of my code since it doesn't name any of my types above that I can see. I tried the big stick of setting all of Boost to "external" (and set the external warning level to 0), but sadly this did not suppress the warning. Wrapping it in a #pragma suppression does hide the warning, which makes me sufficiently happy. But perhaps someone might be interested to poke at it?

2 2

version 1.78.0 compile failed on centos 7 with compiler clang
by David Frank 15 Sep '22

15 Sep '22

error message: boost/spirit/home/classic/phoenix/closures.hpp:274:30: error: default initialization of an object of const type 'const index<0>' without a user-provided default constructor Thanks.

1 0

version 1.78.0 compile failed on centos 7
by David Frank 15 Sep '22

15 Sep '22

error message: boost/spirit/home/classic/phoenix/closures.hpp:274:30: error: default initialization of an object of const type 'const index<0>' without a user-provided default constructor Thanks.

1 0

version 1.78.0 compile failed on centos 7
by David Frank 15 Sep '22

15 Sep '22

error message: boost/spirit/home/classic/phoenix/closures.hpp:274:30: error: default initialization of an object of const type 'const index<0>' without a user-provided default constructor On Saturday, September 3, 2022 at 08:48:54 PM PDT, David Frank <david_frank95(a)yahoo.com> wrote: I'm currently using version 60, it failed to compile with openssl 3.0.5. So I need to upgrade to a version that works. Thanks.

1 0

Redefined macro on Solaris, OmniOS, and SmartOS
by Camden Narzt 11 Sep '22

11 Sep '22

Building code (on Solaris, OmniOS, and SmartOS, using gcc) which includes boost, produces warnings such as the following: In file included from src/boost/config/platform/solaris.hpp:17:0, from src/boost/config.hpp:57, from src/boost/cstdint.hpp:36, from src/code_that_includes_boost.cpp:43: src/boost/config/posix_features.hpp:27:0: warning: "BOOST_HAS_STDINT_H" redefined [enabled by default] # define BOOST_HAS_STDINT_H ^ Not a big deal, but figured I’d report it in case it hadn’t been reported yet.

1 0

which version works with openssl 3.0.5?
by David Frank 04 Sep '22

04 Sep '22

I'm currently using version 60, it failed to compile with openssl 3.0.5. So I need to upgrade to a version that works. Thanks.

2 1

How to build Boost with static ICU via Msys2 / mingw-w64 / gcc on Windows?
by crillion＠tiscali.it 03 Sep '22

03 Sep '22

Hello, I'm trying to build boost 1.80 on windows 10 with the icu provided with msys2 (my goal in particular is that boost locale will build using my installed version of icu). My build platform is msys2 with mingw-w64 / gcc 12.2. By launching pacman -Q on the msys2-msys shell I have seen that I have icu 71.1-2 : (...) glib2 2.72.2-2 gmp 6.2.1-2 gnupg 2.2.36-1 grep 1~3.0-3 gzip 1.12-2 heimdal-libs 7.7.0-3 icu 71.1-2 inetutils 1.9.4-5 info 6.8-4 less 590-2 (...) on my system I have msys2 installed in the following folder C:programsmsys64 and in C:programsmsys64mingw64 there are the following folders : bin etc include lib libexec sbin share ssl var x86_64-w64-mingw32 in the lib folder I have found that there are lib files like libicuio.a, libicudt.a and libicutest.a . I extracted boost and then I've given the usual sequence of commands from the normal cmd shell of windows : for creating b2 : bootstrap.bat gcc for the actual build of boost, I've made the following attempts : b2 --toolset=gcc address-model=64 -sICU_PATH=C:programsmsys64mingw64 b2 --toolset=gcc address-model=64 include=C:programsmsys64mingw64include library-path=C:programsmsys64mingw64lib b2 --toolset=gcc address-model=64 -sICU_PATH=C:programsmsys64mingw64 include=C:programsmsys64mingw64include library-path=C:programsmsys64mingw64lib but none of these works : the build process always writes in its initial phase : (...) has_lzma_cputhreads builds : yes [2] cxx11_decltype : yes [2] cxx11_basic_alignas : yes [2] iconv (libc) : no [2] iconv (separate) : yes [2] icu : no [2] icu (lib64) : no [2] native atomic int32 supported : yes [2] has message compiler : no [2] native syslog supported : no [2] (...) what am I supposed to do to let b2 see the ICU lib files that I have in my msys2 distribution ? Thanks, Marco Voucher MISE per P.IVA e PMI: fino a 2500€ per la Banda Ultralarga. https://casa.tiscali.it/promo/?u=https://promozioni.tiscali.it/voucher_busi…..

1 0

suspendable/resumable/prioritizable task dispatcher
by chris-boostusers＠stankevitz.com 31 Aug '22

31 Aug '22

Hi, Unfortunately I don't have the vocabulary needed to ask this question, but hopefully I'll learn it here. Does Boost have something that will help me with this problem: I have a list of CPU-bound tasks I need to perform. I'll list two of them here: a) compute first zillion digits of pi (low priority) b) add two plus two (high priority) I co_spawn (a). Later, while (a) is running, I co_spawn (b). (a) will be suspended at a "co_suspension_point" so that (b) can take over. Of course when (b) completes, (a) will resume. For bonus points, it will support multiple threads (probably easy) and a task's priority can change over time (probably hard). Thank you! Chris PS: I was recently blown away by the coroutine capability of ASIO: Talking Async Ep1: Why C++20 is the Awesomest Language for Network Programming https://www.youtube.com/watch?v=icgnqFM-aY4

3 3

memory fault when passing var to a coroutine
by Piotr Gosławski 23 Aug '22

23 Aug '22

Hello, Using GCC 10.1 and Boost 1.77 I get a mem fault when executing the following code: #include <iostream> #include <boost/asio.hpp> #include <boost/asio/awaitable.hpp> struct TestStruct { std::string strField; }; boost::asio::awaitable<bool> TestFunction(TestStruct param) { std::cout << param.strField << std::endl; co_return true; } boost::asio::awaitable<void> TestCoroutine() { // This causes mem issue co_await TestFunction(TestStruct{"some string"}); } int main() { boost::asio::io_context io_context; boost::asio::co_spawn( io_context, []() { return TestCoroutine(); }, boost::asio::detached); io_context.run(); return 0; } Also tested with GCC 12.1 and Boost 1.79 - the result is the same ( https://godbolt.org/z/69MKbz7qE) Works if I use a temp variable: boost::asio::awaitable<void> TestCoroutine() { auto testStruct = TestStruct{"some string"}; co_await TestFunction(testStruct); } Or if I add a constructor to test struct: struct TestStruct { explicit TestStruct(const std::string& str) : strField(str) {} std::string strField; }; boost::asio::awaitable<void> TestCoroutine() { co_await TestFunction(TestStruct("some string")); } Is there any coroutines rule that I am violating here? If yes - is there any compiler option I can use to get a warning / error message? Full code with cmake can be found here: https://github.com/piotrgoslawski/mem_issue Thank you

1 0

re：question about compile the boost head file.
by zyx_xzy＠sina.com 23 Aug '22

23 Aug '22

Respeced Mr.Emil, Thank you for your kindly reply. >I can't reproduce this with msvc versions available on godbolt: >https://godbolt.org/z/E8vYWTPf6 Exactly on godbolt,the compilers work well. I test this by myself. Once again, I change to the Microsoft Visual Studio Community 2019 ver. 16.11.18. And compile the program ,the error still exist. >Can you provide a complete error log, including source file and line of the >error? soruce file:info.hppsource code line no:145soruce code:error_info_container_impl * c=new error_info_container_impl;error log:C2259 “boost::exception_detail::error_info_container_impl”: cannot instantiate abstract class, test_boost D:\boost_1_79_0\boost\exception\info.hpp 145 Best regards, zhiyong

2 1

question about compile the boost head file.
by zyx_xzy＠sina.com 20 Aug '22

20 Aug '22

hi anybody, I meet a problem when I try to compile the following program. #include <boost\exception\info.hpp> void main() { return; } The compile environment is Microsoft Visual Studio Community 2022 (64 位) - ver. 17.2.6.Compile error information is that C2259 “boost::exception_detail::error_info_container_impl”: cannot instantiate abstract class.I try many Boost versions,e.g.,boost 79,boost 65,boost64,boost60. They all give errors. Anybody can give me some suggestions? Best regards, zhiyong --------------------------------

2 1

Abwesenheitsnachricht: question about compile the boost head file.
by Sören Textor 20 Aug '22

20 Aug '22

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. ----------------------------------------------- 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.GIL] GCC 12.1.1 fails to compile boost.gil examples with -std=c++20
by B Aleck 18 Aug '22

18 Aug '22

Source: https://www.boost.org/doc/libs/1_80_0/libs/gil/doc/html/_downloads/resize.c… Compile with: g++ -std=c++20 -c gcc version: 12.1.1 The compile successes with -std=c++14 and -std=c++17, only fails with -std=c++20 Same error does not occur on clang Is this a boost bug or gcc bug?

2 1

Enumerating network interfaces and querying their properties
by Kenneth Porter 14 Aug '22

14 Aug '22

Is there a portable way to enumerate network interfaces and query their properties? I don't see anything in ASIO for that. Any recommendations for other libraries? So far the closest I've come is Python's netifaces library. (Maybe someone would like to fork the Python library's C source and bring it into Boost?) <https://github.com/al45tair/netifaces> I've got an app that configures a remote IoT device on the same segment and then opens UDP listeners to listen for a stream of data from the device. The user specifies the hostname or address of the device. I'd like to be able to restrict the listeners to just the interface that the device is connected to. I have two interfaces, one for the LAN and one for devices, and I don't want to listen on the LAN interface. So ideally I'd get the list of interfaces and their addresses and netmasks. I think I also need the routing table. I can then identify which interface will receive the incoming UDP stream.

1 0

Boost support for Arm64/Windows
by Jonathon Penix 12 Aug '22

12 Aug '22

Hi, I am interested in using Boost as a dependency on the Arm64/Windows platform but have been struggling to find information about the status for Boost libraries in general for Arm64/Windows. I am aware of a few specific libraries that directly mention their support status for Arm64/Windows (Boost.Atomic and Boost.Context, for example) or have had Arm64 related patches in their release notes (Boost.Build, for example). Are there any public boards/trackers for the current Boost status or outstanding issues for Boost on Arm64/Windows that I may have missed? Or should platform support be generally assumed to work outside of specific cases like Boost.Context so long as a conformant compiler is provided for the platform? Thanks!

2 1

[release] Boost 1.80.0
by Glen Fernandes 11 Aug '22

11 Aug '22

Release 1.80.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 contains numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.80.0> You can also download directly from: <https://boostorg.jfrog.io/artifactory/main/release/1.80.0/> 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, Michael Caisse

3 2

Broken link to latest code from old ASIO example
by Kenneth Porter 11 Aug '22

11 Aug '22

The directory structure of ASIO changed a bit and now the website pages of samples in old versions no longer direct to the correct page in the latest version: <https://www.boost.org/doc/libs/1_51_0/doc/html/boost_asio/example/icmp/ping…> I wanted to see how to code a ping so I googled for "boost asio ping" and the top result was for 1.51.0. (I never get the latest code, but I can always jump to an older version and then jump from there to the latest. It just didn't work this time.) It did work for 1.67.0 (later in the google search results) which led to the current page: <https://www.boost.org/doc/libs/1_79_0/doc/html/boost_asio/example/cpp03/icm…>

1 0

Fwd: [boost] Upcoming Boost.URL review
by Mateusz Loskot 06 Aug '22

06 Aug '22

---------- Forwarded message --------- From: Klemens Morgenstern via Boost <boost(a)lists.boost.org> Date: Sat, 6 Aug 2022, 15:30 Subject: [boost] Upcoming Boost.URL review To: <boost(a)lists.boost.org> Cc: Klemens Morgenstern <klemensdavidmorgenstern(a)gmail.com> This is a reminder that the boost.url review will start in a week on the 13th. The source code can be found here https://github.com/CPPAlliance/url and the documentation here https://master.url.cpp.al/ . I am looking forward to plenty of reviews. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Boost.Graph: user survey
by Jeremy Murphy 05 Aug '22

05 Aug '22

Dear Boost.Graph users, I'd like to know how you use Boost.Graph. If you know someone that uses Boost.Graph but is not on this mailing list, please forward this survey to them. The purpose of this survey is to help prioritize work on the areas of Boost.Graph that will have the most benefit to the users. I was planning to make a very sophisticated Google Forms survey, but that is so time consuming. These questions should all be taken in the context of using Boost.Graph. - Which operating systems do you use? - Which toolchains do you use? - What is the minimum C++ standard that you require support for? (e.g. 03, 11, 14, etc) - Which features of Boost.Graph are you using? - Which features do you think Boost.Graph is missing? - What are the biggest problems with using Boost.Graph? Purely out of curiosity: - What do you use it for? - If you use it in business (or research), how critical is it? Thanks! Jeremy

4 5