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

Re: [Boost-users] Boost ABI/Linkage of clang vs g++
by DV Henkel-Wallace 10 Jul '20

10 Jul '20

> Date: Thu, 9 Jul 2020 16:44:58 +0100 > From: <pbristow(a)hetp.u-net.com> > > Does b2 -debug-configuration help? > > https://boostorg.github.io/build/manual/master/index.html section 3.3 configuration > > ? > You can use the --debug-configuration option to find which configuration files are actually loaded. Thanks, Paul, this helped me figure out a colleague had modified a .jam file and checked it in. -d

1 0

[ASIO] Using boost::asio::thread_pool with sockets without boost::asio::io_context
by Aniruddh Agarwal 09 Jul '20

09 Jul '20

Hello, One strategy to load-balance I/O processing across multiple threads is to use a single io_context object for multiplexing and to call io_context::run from all threads in the thread pool. This can be set up by, for example, defining a type which holds a vector of threads, all of which are calling io_context::run. My first question is: is this approach of calling io_context::run from several threads somewhat equivalent to using boost::asio::thread_pool as the default execution context and not (explicitly, at least) creating a boost::asio::io_context object at all? Somewhat more specifically, is it safe to define TCP sockets/acceptors/etc. with execution contexts set to a boost::asio::thread_pool instead of io_context, and will that work as expected (i.e., as a single io_context object scheduling tasks out to several threads calling io_context::run would)? -Ani

2 3

Concurrency support in iostream mapped_file_source
by Lloyd 03 Jul '20

03 Jul '20

Hi, Does boost iostream mapped_file_source support concurrent read from multiple threads? What is the best way to implement concurrent read on a performance sensitive application? The file is a read only one and its size is in gigabytes/terabytes Thanks, Lloyd

3 2

[serialization] Backward compatibility problem with 1:73
by Kai Benndorf 25 Jun '20

25 Jun '20

Hi all, we are using boost serialization for writing and reading data and just switched from boost 1:67 to boost 1:73. We now cannot read back the data written with boost 1:67 or prior. We get an archive_exception::input_stream_error exception. Examining the files shows the difference. The old files are starting with 22 serialization::archive 16 The new files are missing this data. Removing it from the files enabled the reading with boost 1:73. But strangely, if trying a small example program (the gps example from the documentation) also boost 1:73 produces this data: 22 serialization::archive 18 Any idea what has changed in between these versions and could cause this problem? Thanks in advance for any hint. Our application uses an own derived archive class. Maybe I have to changed something there? Best regards Kai Benndorf ---------------------------------------------------------------- Kai Benndorf E-Mail: kai.benndorf(a)web.de Zur Maibolte 44 MOBILE: 0151 55627946 32657 Lemgo WORK: 05251 150623 Germany PHONE: 05261 14465 ----------------------------------------------------------------

1 1

[boost][mp11][GIL]
by Debabrata Mandal 18 Jun '20

18 Jun '20

Hi, I am trying to implement a histogram class that will be able to store tuples of any data type. Most likely, I chose std::tuple for the job. So, in brief I used std::tuple as the key type in an unordered_map. I used boost::hash_value to supply the hasher in place of std::hash in the third template argument to unordered_map. Now, fast forwarding to my problem, I want to be able to provide a sub-histogram based on a few axes of the histogram. The code below, quite similar to what I want, refuses to work with msvc-14.0 (coming to it shortly). ----Sample Code---- #include <boost/mp11.hpp> template<typename... T> struct histogram { using type_list = boost::mp11::mp_list<T...>; template<std::size_t... D> void d() { // Error in below line histogram<boost::mp11::mp_at_c<type_list, D>...> f; } }; int main() { histogram<int, int, int, int> f; f.d<1,2>(); return 0; } ---END--- So, msvc-14.0 gives the error (after tracing to the last function call in stack) at the position specified above. The error message which is coming from the AppVeyor logs (since I do not have msvc-14.0) ... C:\projects\boost-root\boost/mp11/utility.hpp(53): error C2971: 'boost::mp11::detail::mp_if_c_impl': template parameter 'C': 'C': a variable with non-static storage duration cannot be used as a non-type argument C:\projects\boost-root\boost/mp11/utility.hpp(38): note: see declaration of 'boost::mp11::detail::mp_if_c_impl' C:\projects\boost-root\boost/gil/histogram.hpp(247): note: see declaration of 'C' ... I am not sure if the issue is with mp11 or the msvc-14.0, but I did find some references which claim a similar issue with the latter case. This links <https://developercommunity.visualstudio.com/content/problem/719235/erroneou…> to a very similar case of the error C2971 which seems to be fixed in the future releases. Also, the code above compiles fine with GCC and Clang. Any comments or suggestions on this are most welcome. Thanks, Deb GSOC 2020 student in Boost.GIL

2 1

Re: [Boost-users] [boost] [review] [text] Text formal review
by Vinnie Falco 17 Jun '20

17 Jun '20

On Fri, Jun 12, 2020 at 10:36 AM Rainer Deyke via Boost <boost(a)lists.boost.org> wrote: > String layer: overall, a solution looking for a problem. I created boost::json::string to use instead of std::string for a couple of reasons: 1. It uses a type-erased, reference counted memory resource instead of Allocator template parameter 2. The class is laid out a certain way to greatly minimize its size 3. The class layout is optimized to keep the size of the enclosing variant (the JSON DOM value type) small 4. The API is the same for all C++ versions (unlike std::string) 5. It is not a class template I would like to know what are the exact _technical_ benefits of Boost.Text's String layer, beyond "because I don't like std::string" Thanks

3 4

Re: [Boost-users] Boost in xeus-cling jupyter kernel
by Giorgino R 16 Jun '20

16 Jun '20

> Ηi there, > > I ve been using boost (geometry) with xeus-cling kernel without any > issues, so far. I install boost from conda forge: > > conda install boost -c conda-forge > > I tried to include odeint.hpp without any issues on my cling environment: > > see also > https://stackoverflow.com/questions/61205040/how-do-i-use-boost-with-the-xe… > > BW > G > > > On Fri, 12 Jun 2020, 19:46 A. de Windt via Boost-users, < > boost-users(a)lists.boost.org> wrote: > >> Hi everyone, >> >> As my first post in this mailing list I would like to ask, has anyone >> tried using boost in a xeus-cling jupyter kernel? Or just cling? >> >> My plan is to use odeint in the jupyter notebook for some simulations. >> However I had issues when I tried to run one of the odeint examples. I >> originally posted my issue on stackoverlfow but didn;t get any feedback. So >> I'm going to mostly copy my original question in this email. >> >> >> https://stackoverflow.com/questions/61205040/how-do-i-use-boost-with-the-xe… >> >> I'm running Pop!_OS (ubuntu derivative) and apt installed boost >> (libboost-all-dev) from the default repositories. I know it has been >> installed properly since I can compile and run the simple boost odeint >> example with GCC. >> >> However when I tried to run the same example inside a jupyter notebook >> using the zeus-cling kernel I got an error while including the odeint >> header. I can recreate the error while executing this code: >> >> #pragma cling add_include_path("/usr/include")#include <boost/numeric/odeint.hpp> >> >> The error message I get is: >> >> In file included from input_line_8:1: >> In file included from /usr/include/boost/numeric/odeint.hpp:22: >> In file included from /usr/include/boost/numeric/odeint/config.hpp:44: >> In file included from /usr/include/boost/config.hpp:48: >> In file included from /usr/include/boost/config/stdlib/libstdcpp3.hpp:78: >> /usr/include/unistd.h:756:28: error: expected function body after function declarator >> extern __pid_t fork (void) __THROWNL; >> ^ >> /usr/include/unistd.h:869:11: fatal error: 'bits/getopt_posix.h' file not found >> # include <bits/getopt_posix.h> >> ^~~~~~~~~~~~~~~~~~~~~ >> Interpreter Error: >> >> From what I understand bits/getopt_posix.h is a GCC only header, thus I >> think the problem might be because the boost headers are configuring >> themselves as if they are compiling under GCC instead of cling/clang. >> >> My solution so far has been to submodule the boost super project into my >> repository and add all the include paths necessary to get odeint and it's >> dependencies to compile. This is fine since odeint is a header only library >> anyways. But I'm pretty sure there is a better solution to this problem. >> >> Thanks in advance and hope to hear from someone back soon. >> >> >> Cheers, >> Aaron M. de Windt >> >> _______________________________________________ >> Boost-users mailing list >> Boost-users(a)lists.boost.org >> https://lists.boost.org/mailman/listinfo.cgi/boost-users >> >

1 0

Boost in xeus-cling jupyter kernel
by A. de Windt 13 Jun '20

13 Jun '20

Hi everyone, As my first post in this mailing list I would like to ask, has anyone tried using boost in a xeus-cling jupyter kernel? Or just cling? My plan is to use odeint in the jupyter notebook for some simulations. However I had issues when I tried to run one of the odeint examples. I originally posted my issue on stackoverlfow but didn;t get any feedback. So I'm going to mostly copy my original question in this email. https://stackoverflow.com/questions/61205040/how-do-i-use-boost-with-the-xe… I'm running Pop!_OS (ubuntu derivative) and apt installed boost (libboost-all-dev) from the default repositories. I know it has been installed properly since I can compile and run the simple boost odeint example with GCC. However when I tried to run the same example inside a jupyter notebook using the zeus-cling kernel I got an error while including the odeint header. I can recreate the error while executing this code: #pragma cling add_include_path("/usr/include")#include <boost/numeric/odeint.hpp> The error message I get is: In file included from input_line_8:1: In file included from /usr/include/boost/numeric/odeint.hpp:22: In file included from /usr/include/boost/numeric/odeint/config.hpp:44: In file included from /usr/include/boost/config.hpp:48: In file included from /usr/include/boost/config/stdlib/libstdcpp3.hpp:78: /usr/include/unistd.h:756:28: error: expected function body after function declarator extern __pid_t fork (void) __THROWNL; ^ /usr/include/unistd.h:869:11: fatal error: 'bits/getopt_posix.h' file not found # include <bits/getopt_posix.h> ^~~~~~~~~~~~~~~~~~~~~ Interpreter Error: >From what I understand bits/getopt_posix.h is a GCC only header, thus I think the problem might be because the boost headers are configuring themselves as if they are compiling under GCC instead of cling/clang. My solution so far has been to submodule the boost super project into my repository and add all the include paths necessary to get odeint and it's dependencies to compile. This is fine since odeint is a header only library anyways. But I'm pretty sure there is a better solution to this problem. Thanks in advance and hope to hear from someone back soon. Cheers, Aaron M. de Windt

2 1

Re: [Boost-users] [boost] [review] [text] Text formal review
by Emil Dotchevski 13 Jun '20

13 Jun '20

On Fri, Jun 12, 2020 at 10:36 AM Rainer Deyke via Boost < boost(a)lists.boost.org> wrote: > String layer: overall, a solution looking for a problem. I tend to agree with this but I had assumed there is a reason why it exists. Zach indicated that he doesn't care much about it, so it probably should be deleted, but I don't feel strongly about this because there are plenty of C++ APIs which define their own string type, and I don't see this as a problem. In C++, we have many of everything.

1 0

[review] [text] Text review begins June 11
by Glen Fernandes 12 Jun '20

12 Jun '20

The Boost formal review of Zach Laine's Unicode library, Text, commences on June 11th and concludes June 20th. We welcome the participation of Boost developers and users, and the C++ community. Quote: This library includes three layers: - The string layer, a set of types that constitute "a better std::string" - The Unicode layer, consisting of the Unicode algorithms and data - The text layer, a set of types like the string layer types, but providing transparent Unicode support Code: https://github.com/tzlaine/text Docs: https://tzlaine.github.io/text Text requires C++14 or higher, and supports GCC 5+, Clang 3.6+, and MSVC 2017. Zach initially presented the library at C++Now in 2018. He also intends to standardize a library solution for Unicode based on this work. Talk: https://www.youtube.com/watch?v=944GjKxwMBo Slides: https://tinyurl.com/boost-text-slides Try the library today, and please consider submitting a review, or even contributing to the discussion next week. Glen

4 3