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

Boost-1.71.0 upgrade issue
by Tej Kumar 28 Jul '20

28 Jul '20

Hi Team, Hope you guys are doing well. I am trying to upgrade Boost to 1.71.0 version. My code is compiling and building successfully but during test run i see below error. Error seems to be related with boost chrono, even though i have included boost_chrono lib in my makefile. *undefined symbol: _ZN5boost6chrono12steady_clock3nowEv* It will be a great help if you guys can suggest something here. Thanks & Regards, Tej

2 3

[Graph] Unable to get the edge_color in depth_first_search
by Ashish Kumar 27 Jul '20

27 Jul '20

Hello, First of all, I am new to Boost Graph Library. So, there might be a simpler or easier fix to the problem I am facing. I am trying to get the edge color after executing the boost::depth_first_search algorithm on the graph. For that, I created an edge color map and passed it to the function. Also, to log the colors of the edges, I made a visitor class, passed the color of the edge to it, and printed it to the standard output stream, for the tree_edge, back_edge, etc. But, for every edge, the value of color comes out to be 0. So, I am not able to get the color of every edge. A small snippet of how I am calling the depth_first_search function: depth_first_search(graph, visitor(dfs_visitor(root, visited_order, colors, graph)) .edge_color_map(&colors) .root_vertex(root)); The complete code along with the visitor class can be found here: https://gist.github.com/krashish8/5f8d8e613e189857bd2b0fd46dd02b29 Please suggest any possible solution to this problem. Thank you, Ashish Kumar.

1 0

[boost] Clang on Windows - No Autolink?
by Klaim - Joël Lamotte 27 Jul '20

27 Jul '20

Hi, am I correct that autolinking is not supported by Boost when using Clang on Windows? To be clear, I'm talking about both clang++ and clang-cl drivers. The behavior I observe suggests that I am correct but looking at the autolink.hpp header I didn't understand how it decides if it should work or not. A. Joël Lamotte

3 8

Two Graphs Common Spanning Trees Issue [GSoC]
by Prakash Tiwari 24 Jul '20

24 Jul '20

Hello, Community Members and developers, I'm student of Google Summer Of Code and contributing to the pgRouting <https://github.com/pgRouting/pgrouting/>[1]. I need to use boost algorithm boost::two_graphs_common_spanning_trees. I have gone through the documentation and try to use it (with help of example.cpp) But I found that this algorithm is not returning the expected results. I have mentioned the example that I have used and explained the expected and given results <https://github.com/prakashupes/ProposalCodes/issues/1>.[2] So, please try to figure out that is it a bug implemented algorithm or It might be possible that I'm using the algorithm in the wrong way. Thanks Prakash Tiwari [1].https://github.com/pgRouting/pgrouting/ [2]. https://github.com/prakashupes/ProposalCodes/issues/1

1 0

jpeg resize - file size increases
by Lloyd 24 Jul '20

24 Jul '20

Hi, We tried boost gil resize example to experiment with scaling down a jpeg image file. For some images, this causes the size of the file to increase. We are using bilinear_sampler algorithm. Our aim to reduce the input image size so as to save storage/network bandwidth. Quality can be compromised to a certain extent. Which algorithm/method should we use? The code fragment is given below:- boost::gil::rgb8_image_t img; boost::gil::read_and_convert_image(InStream, img, T()); float width = (float)(img.width() * Ratio) / 100; float height = (float)(img.height() * Ratio) / 100; boost::gil::rgb8_image_t resizedImg(width, height); boost::gil::resize_view(const_view(img), view(resizedImg), boost::gil::bilinear_sampler()); boost::gil::write_view(OutStream, boost::gil::const_view(resizedImg), T()); Thanks, Lloyd

2 4

bjam resources
by Antonis Polykratis 18 Jul '20

18 Jul '20

Hello, are there any bjam tutorials documentation about how I could create a project using bjam? Thanks

3 2

Boost ABI/Linkage of clang vs g++
by DV Henkel-Wallace 17 Jul '20

17 Jul '20

boost-users(a)lists.boost.org We build with clang++-10 w/libc++.a and g++-10 w/libstdc++.a, so build a copy of boost in each configuration as well. This works great on the Mac development machines but the clang case doesn't generate the correct linkage on the Linux deployment machines. The correct clang linkage is std::__1::basic_string... but boost builds with std::__cxx11::basic_string Here's the linkage of libc++: $ objdump -T /usr/lib/llvm-10/lib/libc++.so.1|c++filt|grep ::basic_string|head -1 0000000000057450 g DF .text 0000000000000048 Base std::__1::locale::locale(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) Notice: std::__1::basic_string< ... When compiling my own code with clang++-10 the correct symbol is generated: $ nm options.cc.o |c++filt |fgrep __ |fgrep ::set_option_name |head -1 0000000000000000 W fmt::v6::basic_format_context<std::__1::back_insert_iterator<fmt::v6::internal::buffer<char> >, char>::iterator... Notice std::__1:: ... However the boost object have the wrong symbol name: $ nm 3P/llvm/lib/libboost_program_options.a |c++filt |fgrep __ |fgrep ::basic_string |head -1 0000000000000000 W boost::program_options::unknown_option::unknown_option(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) Notice std::__cxx11::basic_string< ... I'm compiling boost this way: export CC=clang CXX="clang++ -stdlib=libc++" CXXSTD=c++20 ; ./b2 stdlib=libc++ toolset=clang boost.locale.icu=off boost.locale.std=off --with-atomic --with-chrono --with-date_time --with-headers --with-locale --with-log --with-program_options --with-random --with-regex --with-system --with-thread threading=multi -sNO_COMPRESSION=1 link=static install It's 1.73.0

5 6

[release] Boost 1.74.0 beta 1 released
by Marshall Clow 16 Jul '20

16 Jul '20

Boost release 1.74.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.74.0.beta.1/source/> The SHA256 checksums are as follows: 577a6b575ff2c227e14cce1b929c73d969475e58f3d2ab2901ad234f773bbd12 boost_1_74_0_b1.7z ba09c72dc848e7c0904922967014d853897b5a634926c910cc3b1fd627c31605 boost_1_74_0_b1.tar.bz2 2ccdc39efa076822cf1b359f9449f9d07707f3e27a18b393297b25885a9ff45b boost_1_74_0_b1.tar.gz c267c450166e040a374eaddab5e583cef09f6c3fe96a4db826172d0315c38dd5 boost_1_74_0_b1.zip For details of what's in the release, see < https://www.boost.org/users/history/version_1_74_0.html>. Please download the beta, give it a try, and report any problems you encounter. Issues that were found during the beta release process and will be fixed for the final 1.74.0 release: * The Boost.STLInterfaces documentation was left out of the beta. * Some of the Boost.Geometry documentation files have very long names; this could cause problems on platforms (like Windows) with shorter limits on path lengths. * There is a compile error in Boost.ASIO when compiling with 32-bit MSVC-14.2 with BOOST_BEAST_NO_TS_EXECUTORS. Thanks, -- The Boost Release Team

1 0

[release] Boost 1.74.0 Beta 1 Release Candidate 1
by Marshall Clow 14 Jul '20

14 Jul '20

The release candidates for the first 1.74.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.74.0.beta.1/source/ The release notes are not yet available. The SHA256 checksums are as follows: 577a6b575ff2c227e14cce1b929c73d969475e58f3d2ab2901ad234f773bbd12 boost_1_74_0_b1_rc1.7z ba09c72dc848e7c0904922967014d853897b5a634926c910cc3b1fd627c31605 boost_1_74_0_b1_rc1.tar.bz2 2ccdc39efa076822cf1b359f9449f9d07707f3e27a18b393297b25885a9ff45b boost_1_74_0_b1_rc1.tar.gz c267c450166e040a374eaddab5e583cef09f6c3fe96a4db826172d0315c38dd5 boost_1_74_0_b1_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Boost Release Managers

3 4

bjam using boost-1.77
by Cho-Kuen Ng 11 Jul '20

11 Jul '20

I used to use a very old version of bjam and wanted to switch to the most recent version 1.77. When I use the new bjam, I encounter the following problems. o I have 2 projects with the same id, the error message is error: at nml/unit_test/Jamfile:1 error: Attempt to redeclare already registered project id '/test'. error: Original project: error: Name: Jamfile</Users/cho/work/distmesh/unit_test> error: Module: Jamfile</Users/cho/work/distmesh/unit_test> error: Main id: /test error: File: distmesh/unit_test/Jamfile error: Location: distmesh/unit_test error: New project: error: Module: Jamfile</Users/cho/work//nml/unit_test> error: File: nml/unit_test/Jamfile error: Location: nml/unit_test After I changed the id in one project, the errors disappeared. o I do bjam again, I have this error /Users/cho//doc/boost/boost_1_73_0/tools/build/src/build/generators.jam:1127: in ensure-type from module generators error: target { PNCDF_Variable.C. } has no type Once I changed the C extension to cpp, the error disappeared. I don't have these problems using the old bjam. Are there syntax changes in the Jamfile? Please help. Thanks, Cho

1 0

[InterProcess] receiving notification when an item is added to the message queue
by Sean Farrow 11 Jul '20

11 Jul '20

Good afternoon, I am looking to use the message queue in the Interprocess library to communicate between two Windows processes. I was wondering whether there was an in-built mechanism to signal to the process reading from the queue that a message is available for consumption. If there isn't anything in-built, I was wondering what the best way to do this is and whether anybody has any working sample code they would be willing to share? Any help appreciated as always. Kind regards Sean.

2 1

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

[asio] tcp non blocking sync read query (bug?)
by Keith Robinson 11 Jun '20

11 Jun '20

Hi, I'm sending data from one process to another using a tcp connection. Sender use scatter-gather to send the data using 3 buffers (total just over 2000 bytes). The reader uses 2 separate sync reads to read the data (using the asio free function read()) using a non blocking socket. Sometimes everything is fine, the 2 reads return the amount of data requested, but sometimes I see strange behaviour. I'm trying to work out whether I am doing something wrong, or whether I've stumbled across a bug. When it goes wrong for me, the second read always returns less data than I requested, along with the error code 'would_block'. I then loop, performing further reads (using the same buffer as before), eventually (one read, or multiple reads later) the read function returns the remainder of the data, but still with the error code 'would_block' set. However, when I check the contents of the buffer, it is not what I expected. I think, but haven't been able to confirm, that the start of the buffer is not the start of the data. 1. Is it expected that the read() free function, when the socket is non blocking, can return less data than requested, along with the error code 'would_block'? 2. If it is expected, does the buffer passed in subsequent reads have to be adjusted to read only the remaining about of data? 3. If the buffer does have to be changed to only read what is left, how does this work with scatter-gather reads using multiple buffers? As a little bit of extra info, I confirmed using tcpdump that the correct data is sent/received, although it arrives in 2 chunks (MTU size of 1500). This is on Linux using Boost 1.73.0. Cheers, Keith

3 3

[review] [text] Text formal review
by Glen Fernandes 11 Jun '20

11 Jun '20

Dear Boost community, The formal review of Zach Laine's Unicode library, Text, begins today (June 11th) and ends on June 20th. The library provides 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 The master branch of the repository will be frozen for the duration of the review. 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 We encourage your participation in this review. At a minimum, kindly state: - Whether you believe the library should be accepted into Boost * Any conditions for acceptance - Your name and knowledge of the problem domain. You are strongly encouraged to also provide additional information: - What is your evaluation of the library's: * Design * Implementation * Documentation * Tests * Usefulness - Did you attempt to use the library? If so: * Which compiler(s) * What was the experience? Any problems? - How much effort did you put into your evaluation of the review? Even if you are not submitting a formal review, your feedback on the library is welcome. Glen

1 0

Impossible to download a boost source from bintray: 403 Forbidden
by Eisuke Kawashima 08 Jun '20

08 Jun '20

Dear All, I cannot download a boost source from bintray, e.g., https://dl.bintray.com/boostorg/release/1.73.0/source/boost_1_73_0.tar.bz2 returns 403 Forbidden. OTOH, sourceforge works: https://sourceforge.net/projects/boost/files/boost/1.73.0/boost_1_73_0.tar.…. Best -- Eisuke Kawashima e.kawaschima+boost(a)gmail.com

3 4

[review][LEAF] Review period is over
by Michael Caisse 04 Jun '20

04 Jun '20

I apologize for not sending this out earlier. The review period is officially complete. A few people have contacted me about completing reviews that they in the middle of and I will be waiting until after this coming weekend to publish the review results. Thank you to those that joined the conversation and provided a review. michael -- Michael Caisse Ciere Consulting ciere.com

1 0