July 2019 - Boost - lists.preview.boost.org

[release] Boost 1.71.0 Beta 1
by Michael Caisse 26 Jul '19

26 Jul '19

Boost release 1.71.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.71.0.beta1.rc1/source/> The SHA256 checksums are as follows: 451adc4f199c73e995e541f38c4dbd51faf4ce0db15537136ffd5213a1be5e55 boost_1_71_0_b1_rc1.7z a93d7066fc1514995aec0e726532a219447dd39b0ffa7cb97ca5736f16b0488b boost_1_71_0_b1_rc1.tar.bz2 34743b80466463e0c1b7fc71b677f326bdc242fe0b87a9c1599b6f7ea6e5c0cb boost_1_71_0_b1_rc1.tar.gz 5cd448bddc8394469391306e0ccada0a8f88c5c6cf8ec775ddf8e56adef8bbc2 boost_1_71_0_b1_rc1.zip For details of what's in the release, see <http://www.boost.org/users/history/version_1_71_0.html>. Note: Having some trouble getting the web page updated... check back with it soon. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

9 15

Boost proposals
by VALERIU SMERICA 26 Jul '19

26 Jul '19

Hello. Is it possible to propose some data structures to be part of Boost that use code under the Apache 2.0 license? Are there any legal issues with this? I heard Apache 2.0 license was pretty permissive. Thanks.

1 0

boost::serialization optional does not use boost::serialization::access
by Janek Kozicki 25 Jul '19

25 Jul '19

Hi, this simple program will not compile. The only way to make it work is to make a public default constructor. This defeats the purpose of boost::serialization::access. I tried to fix <boost/serialization/optional.hpp> but I couldn't get it to correctly call the access::construct(); Please help. // g++ -o serialize_optional /tmp/serialize_optional.cpp -lboost_serialization #include <fstream> #include <iostream> #include <boost/serialization/nvp.hpp> #include <boost/serialization/serialization.hpp> #include <boost/archive/xml_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/serialization/access.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/optional.hpp> #include <boost/optional.hpp> class Foo { public: Foo(int k) : i(k) {} friend std::ostream& operator<<(std::ostream& os, Foo const& foo) { return os << "Foo { " << foo.i << " }"; } private: Foo() : i(-1) {}; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int){ #define N(a) BOOST_SERIALIZATION_NVP(a) ar & N(i); #undef N }; int i; }; int main() { using Data = boost::optional<Foo>; std::cout << "Boost version: " << BOOST_VERSION << "\n"; { auto f = Data(133); std::ofstream os("test.xml"); boost::archive::xml_oarchive oa(os); oa << boost::serialization::make_nvp("f", f); } { Data g; std::ifstream is("test.xml"); boost::archive::xml_iarchive ia(is); ia >> boost::serialization::make_nvp("f", g); std::cout << g.get() << "\n"; } } best regards Janek Kozicki

2 4

[gil] Missing doc/html/ files from Boost 1.70
by Mateusz Loskot 24 Jul '19

24 Jul '19

Hi, I'm following up this old report of mine [1] about missing GIL docs. Apparently, GIL documentation was not generated during the release process, so no files were copied wherever they should be. The documentation is missing from: - boost_1_70_0 source archives - https://www.boost.org/doc/libs/1_70_0/libs/gil/ Is it possible to fix the website at least, redirect it to valid URL? Can I fix it myself? How? [1] https://lists.boost.org/Archives/boost/2019/04/245985.php Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 1

[locale] Loss of precision (C4244) warnings in MSVC 64-bit build
by Kenneth Porter 24 Jul '19

24 Jul '19

Building with MSVC compilers for 64-bit results in several C4244 warnings in api.hpp, due to passing the difference of two pointers (ptrdiff_t) to Win APIs expecting an int. Patch here: <https://github.com/boostorg/locale/issues/42> Using this command with the recent 1.71.0 beta: call .\bootstrap.bat --without-python .\b2 --without-python toolset=msvc-14.2,msvc-14.0,msvc-12.0,msvc-10.0 runtime-link=shared,static address-model=32,64

2 1

[release] Boost 1.71.0 Beta 1 - déjà vu
by Michael Caisse 23 Jul '19

23 Jul '19

Note: The previous email announcement still had the rc1 tag in the filenames. This version of beta1 is identical in content to beta1 rc1. Boost release 1.71.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.71.0.beta1/source/> The SHA256 checksums are as follows: 451adc4f199c73e995e541f38c4dbd51faf4ce0db15537136ffd5213a1be5e55 boost_1_71_0_b1.7z a93d7066fc1514995aec0e726532a219447dd39b0ffa7cb97ca5736f16b0488b boost_1_71_0_b1.tar.bz2 34743b80466463e0c1b7fc71b677f326bdc242fe0b87a9c1599b6f7ea6e5c0cb boost_1_71_0_b1.tar.gz 5cd448bddc8394469391306e0ccada0a8f88c5c6cf8ec775ddf8e56adef8bbc2 boost_1_71_0_b1.zip For details of what's in the release, see <http://www.boost.org/users/history/version_1_71_0.html>. Note: Having some trouble getting the web page updated... check back with it soon. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

2 1

[BOOST] Boost fusion testcase fails with llvm and gcc when optimization enabled
by Jaydeep Chauhan 22 Jul '19

22 Jul '19

Hi Devs, consider below boost testcase, boost_1_70_0/libs/fusion/test/functional/invoke.cpp when compiles with optimization enabled, $g++ -O2 -I./boost_1_70_0 boost_1_70_0/libs/fusion/test/functional/invoke.cpp $./a.out ./boost_1_70_0/libs/fusion/test/functional/invoke.cpp(391): test 'that.data == fusion::invoke(& members::data, fusion::join(sv_obj_c_ctx,seq))' failed in function 'void test_sequence_n(Sequence&, mpl_::int_<0>) [with Sequence = boost::fusion::vector<>]' ./boost_1_70_0/libs/fusion/test/functional/invoke.cpp(401): test 'that.data == fusion::invoke(& members::data, fusion::join(sv_obj_c_d_ctx,seq))' failed in function 'void test_sequence_n(Sequence&, mpl_::int_<0>) [with Sequence = boost::fusion::vector<>]' ./boost_1_70_0/libs/fusion/test/functional/invoke.cpp(391): test 'that.data == fusion::invoke(& members::data, fusion::join(sv_obj_c_ctx,seq))' failed in function 'void test_sequence_n(Sequence&, mpl_::int_<0>) [with Sequence = boost::fusion::list<>]' ./boost_1_70_0/libs/fusion/test/functional/invoke.cpp(401): test 'that.data == fusion::invoke(& members::data, fusion::join(sv_obj_c_d_ctx,seq))' failed in function 'void test_sequence_n(Sequence&, mpl_::int_<0>) [with Sequence = boost::fusion::list<>]' 4 errors detected. And When compiled without any optimization $g++ -O0 -I./boost_1_70_0 boost_1_70_0/libs/fusion/test/functional/invoke.cpp $./a.out No errors detected. $g++ --version Target: x86_64-pc-linux-gnu Configured with: ../gcc-9.1.0/configure -- --enable-languages=c,c++ --disable-libquadmath --disable-libquadmath-support --disable-werror --disable-bootstrap --enable-gold Thread model: posix gcc version 9.1.0 (GCC) Here we demonstrated the test case with g++ but same can be seen with clang++. When analyzed further we have seen that this is [ boost_1_70_0/boost/fusion/functional/invocation/invoke.hpp:139 ] trying to return local address, which is undefined behavior. And that lead to above test-case failure. So either we have to modify test-case to pass as reference or disable it.But before going ahead like to know your thought/suggestions? Thanks, Jaydeep

1 0

Innocent but annoying warning in Boost QVM library
by Luigi Castelli 19 Jul '19

19 Jul '19

Hi Emil and all, when compiling Boost QVM, compilation succeeds but I get this warning: filename: quat_operations.hppwarning: Declaration shadows a typedef in function 'boost::qvm::axis_angle' A declaration in line 1438 shadows one in line 1414 Could this be solved for the next update?Thanks - Luigi

2 1

Boost log to limit log file maximum file size
by JH 19 Jul '19

19 Jul '19

H Andrey and all, Can the log file be configured to set up the file size cap, when the log file reaches to the maximum file size, it deletes it and starts a new log file not rotates it? Thank you. - jupiter

2 1

Lambda testcase fails when optimization enabled in gcc and llvm
by navya deepika garakapati 19 Jul '19

19 Jul '19

Hi Devs, consider below reduced testcase from boost lamda. $cat result_of_tests.cpp #include <boost/lambda/lambda.hpp> #include <stdio.h> template<class A, class F> typename boost::result_of<F(A)>::type apply1(F f, A b) { return f(b); } using namespace boost::lambda; int main(int, char *[]) { int one = 1; int d= (apply1<int>(_1 ,one) == 1); printf("\n%d\n",d); return 0; } when compiled with optimization O2 $g++ result_of_tests.cpp -I ./boost_1_70_0 -O2 $./a.out 0 And,when we compile same testcase with O0 $g++ result_of_tests.cpp -I ./boost_1_70_0 -O0 $./a.out 1 The above testcases is demonstrated with g++ compiler but behavior is same on clang as well. so we thought that this may be boost testcase issue. When we replace , int d= (apply1<int>(_1 ,one) == 1); with int d= (apply1<int&>(_1 ,one) == 1); testcase gives correct result with or without optimization. Wanted to confirm here,is it valid testcase or we have to modify testcase as per above? Thanks, Navya

3 5