September 2022 - Boost - lists.preview.boost.org

1.80.0 issue with Clang 15
by Peter Dimov 10 Sep '22

10 Sep '22

I'm getting multiple reports that ContainerHash 1.80.0 doesn't compile with Clang 15, due to the following change to Config unfortunately not being part of the 1.80.0 release: https://github.com/boostorg/config/commit/f0af4a9184457939b89110795ae2d2935… Since the plans for 1.80.1 have been abandoned, it's not clear what we can do about that except probably updating the Known Issues section.

3 2

How to know the connected server is down ?
by Raghu Huchchannavar 07 Sep '22

07 Sep '22

Hi, I am using the boost socket for the client and server connection. i set the socket option as below boost::asio::socket_base::keep_alive option(true); tcp_socket->set_option(option); I am able to connect the client to the server. Suppose after some time the server goes down. How do I get that information without sending any read/write request? 1. Now I don't know how to check if the client is down ? 2. Do I get the signal that the client is down? (Without reading or writing at the client )? . If yes, how to handle it. Please help me with this ... -- Regards Raghavendra Huchchannavar.

3 2

[Leaf] Unable to compile with particular flags.
by Misha Doter 06 Sep '22

06 Sep '22

Hi. I have a project ( https://github.com/rokoDev/buffer/tree/develop ) where I want to use Boost.Leaf as an error handling mechanism. And in addition I need to compile it by clang compiler with flags "-Werror -Wshadow-all -Wsign-conversion -Wextra" but it turned out that Boost.Leaf was unable to compile with these flags. So I have created a git fork( https://github.com/rokoDev/leaf/tree/clang_flags ) from official Boost.Leaf ( https://github.com/boostorg/leaf ) and made minimal changes which allowed me to build it with those flags. Also I have run all unit tests for Boost.Leaf on MacOS with success. Is it possible to accept my changes(probably with appropriate corrections if either) in order to allow compilation of any project with the same compiler flags as in my project but using the official version of Boost.Leaf?

3 4

Regression Tests Failing for Develop
by Tom Kent 05 Sep '22

05 Sep '22

I just noticed that all regression tests have been failing for develop since somewhere around Aug 24. https://www.boost.org/development/tests/develop/developer/summary.html I'm not sure if this is it or not, but I see an error in my ../libs/multiprecision/test/Jamfile.v2:1020: Unescaped special character in argument <toolset>msvc:<cxxflags>-constexpr: steps10000000 ../libs/multiprecision/test/Jamfile.v2:1021: Unescaped special character in argument <toolset>msvc:<cxxflags>-constexpr: steps10000000 /var/boost/run/boost_bb/src/build/project.jam:259: in find-jamfile from module project error: Unable to load Jamfile. error: Could not find a Jamfile in directory '../libs/python/build'. error: Attempted to find it with pattern '[Bb]uild.jam [Jj]amfile.v2 [Jj]amfile [Jj]amfile. [Jj]amfile.jam'. error: Please consult the documentation at 'https://www.bfgroup.xyz/b2/'. Then the output shows: # Starting tests ("/var/boost/run/boost_bb/src/engine/b2" "-sBOOST_BUILD_PATH=/var/boost/run:/var/boost/run/boost_bb/src " "-sBOOST_ROOT=/var/boost/run/boost_root" "--boost=/var/boost/run/boost_root" "--boost-root=/var/boost/run/boost_root" "--boost-build=/var/boost/run/boost_bb/src" "--debug-configuration" -l300 toolset=clang-13~c++20 -d2 preserve-test-targ ets=off --dump-tests -j8 address-model=64 debug-symbols=off --remove-test-targets -m64 "--build-dir=/var/boost/run/resul ts" >>"/var/boost/run/results/bjam.log" 2>&1)... # Running Boost.Build tests Traceback (most recent call last): File "run.py", line 71, in <module> runner(root) File "/var/boost/run/boost_regression_src/regression.py", line 286, in __init__ self.main() File "/var/boost/run/boost_regression_src/regression.py", line 623, in main getattr(self,action_m)() File "/var/boost/run/boost_regression_src/regression.py", line 588, in command_regression self.command_test() File "/var/boost/run/boost_regression_src/regression.py", line 367, in command_test self.command_test_boost_build() File "/var/boost/run/boost_regression_src/regression.py", line 409, in command_test_boost_build "boost/bin.v2/libs/any/test/any_test.test")); OSError: [Errno 2] No such file or directory: '/var/boost/run/results/boost/bin.v2/libs/any/test/any_test.test' But I think that's just a generic failure. Thanks, Tom

2 1

[Units] Incorrect definitions for torque, newton_meter
by Albert Dvornik 04 Sep '22

04 Sep '22

#include <iostream> #include "boost/units/systems/si.hpp" #include "boost/units/systems/si/io.hpp" using boost::units::quantity; using boost::units::si::torque; using boost::units::si::newton_meter; using boost::units::si::newton; using boost::units::si::meter; using boost::units::si::radian; int main() { // works fine: quantity<torque, double> tau0 = 0.0 * newton_meter; // SURPRISE: compilation fails because newton_meter is not the // same as newton*meter! // quantity<torque, double> tau1 = 0.0 * newton * meter; // Compilation succeeds even though the units on the RHS do not // represent torque but torsional stiffness! quantity<torque, double> tau2 = 0.0 * newton * meter / radian; // newton * meter should give us a quantity with units of Newton- // meters, i.e. m^2 kg s^-2. What this actually prints out is "0 J", // which is reasonable since dimensionally J is the same as N m. std::cout << boost::units::to_string(0.0 * newton * meter) << std::endl; // One might hope that newton_meter would be the same thing as // newton * meter. Instead, the result is "0 m^2 kg s^-2 rad^-1" std::cout << boost::units::to_string(0.0 * newton_meter) << std::endl; // The "torque" unit is also messed up in the same way. std::cout << boost::units::to_string(torque()) << std::endl; }

5 8

additional math-functions
by Gero Peterhoff 04 Sep '22

04 Sep '22

Hello, I would like to add several missing math functions in boost or specialize/overload existing ones for more types. These should be constexpr if possible. My problems with the concrete implementations are: - Which C++ standard to use C++11/14/17/20/23 ? - Should these be implemented in ccmath and math ? a) ccmath requires C++17 (eg "if constexpr"), so it is not possible to simply call the ccmath version in math, since math requires C++11. b) On the other hand, the math functions are already included in the standard (since C++11), so it wouldn't be necessary to continue to provide them (especially since they are not constexpr). Where and how exactly and with which C++ standard can I add the functions ? thx Gero

4 10