- Boost - lists.preview.boost.org

[range] master broken in latest MSVC
by Vinnie Falco 26 Apr '18

26 Apr '18

I'm using the latest release of Visual Studio and I get these errors from the master superproject: 8>c:\users\vinnie\src\boost\boost\range\concepts.hpp(257): error C3646: 'n': unknown override specifier 8>c:\users\vinnie\src\boost\boost\range\concepts.hpp(264): note: see reference to class template instantiation 'boost::range_detail::RandomAccessIteratorConcept<Iterator>' being compiled 8>c:\users\vinnie\src\boost\boost\range\concepts.hpp(257): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int This issue exactly describes the problem: <https://github.com/boostorg/range/issues/68> Thanks

2 1

[lexical_cast] calling virtual function in constructor of `boost::detail::basic_pointerbuf`
by Andrzej Krzemienski 25 Apr '18

25 Apr '18

Hi everyone, Following the recommendation, I am posting a note about the filed issue in lexical_cast: https://svn.boost.org/trac10/ticket/13540#ticket clang-tidy reports (while checking the code that uses boost::lexical_cast) a virtual function is called in the default constructor of class template boost::detail::basic_pointerbuf. (Function setbuf() is declared virtual in base class.) This might be an indication of a bug. If not, I would recommend using a different construct that avoids confusion, for instance declaring the function override final in newer versions of C++, or providing another function with different name but with the same semantics as the overriding setbuf(). Here's the link to the offending call: https://github.com/boostorg/lexical_cast/blob/develop/include/boost/detail/… Regards, &rzej;

1 0

Fornux C++ Superset
by Phil Bouchard 24 Apr '18

24 Apr '18

Greetings, Because there was a conflict of interests in the past then I feel obliged to give an update regarding the status of the "Fornux C++ Superset" (formerly "Fornux C Leak Detector"). This way corporations will not claim ownership of the idea. - Fornux C++ Superset harnesses the power of Clang. - It now supports, as you have guessed, C++98 syntax. - It's deterministic so it will not slow down your application randomly like with Java. - You can see attached examples memory leaks in C & C++ with cyclic references which are correctly handled and the memory usage never increases. Like I mentioned previously, I am working hard on a free version I will be able to share in a month or two. Regards, Phil Bouchard www.fornux.com

2 2

[interprocess] Enhancment for Boost.Interprocess on Windows
by Aliaksandr Zaitsau 23 Apr '18

23 Apr '18

Hello, My colleague at work suggests an enchancement for Boost.Interprocess for detecting unique boot on Windows. Currently in Boost.Interprocess we have 3 implementations: 1. Using COM. It is marked as incorrect in case of hibernation. 2. Current default implementation using system events log is incorrect since lots of computers will not have expected event in system event log. 3. There is some new for me implementation using reading Windows registry. It is disabled by default. Question 1 What Windows versions are expected to be supported by current library version? What about Windows XP? Earlier Windows? Question 2 What is the status of third implementation via registry? Question 3 It seems strange for him third implementation needs 2 registry values for creating unique id. First of them looks enough for this purpose. And another one may be not present on some Windows. Who may he speak to get technical details why this implementation looks like this? He has an idea how to implement unique boot id better than first and second implementations. He tried to email Ion Gaztanaga directly, but without any responce. Is it good idea to create PR on GitHub before getting any details from Ion? Best regards, Alexander Zaitsev

2 1

UUID broken with Boost 1.67 and VS2015?
by rleigh＠codelibre.net 23 Apr '18

23 Apr '18

In a source file including: #include <boost/uuid/uuid.hpp> #include <boost/uuid/uuid_io.hpp> #include <boost/uuid/uuid_generators.hpp> and then calling boost::uuids::to_string(boost::uuids::random_generator()()) I'm getting: [15/26] Linking CXX executable test\ome-files\ometiffwriter.exe FAILED: test/ome-files/ometiffwriter.exe cmd.exe /C "cd . && "C:\Program Files\CMake\bin\cmake.exe" -E vs_link_exe --intdir=test\ome-files\CMakeFiles\ometiffwriter.dir --manifests -- C:\PROGRA~2\MICROS~1.0\VC\bin\amd64\link.exe /nologo test\ome-files\CMakeFiles\ometiffwriter.dir\ometiffwriter.cpp.obj test\ome-files\CMakeFiles\ometiffwriter.dir\tiffsamples.cpp.obj /out:test\ome-files\ometiffwriter.exe /implib:test\ome-files\ometiffwriter.lib /pdb:test\ome-files\ometiffwriter.pdb /version:0.0 /machine:x64 /debug /INCREMENTAL /subsystem:console lib\ome\files\ome-filesd.lib lib\ome\test\ome-testd.lib C:\build\b\stage\lib\ome-xmld.lib C:\build\b\stage\lib\boost_random-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\tiffd.lib C:\build\b\stage\lib\ome-commond.lib C:\build\b\stage\lib\boost_iostreams-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_log-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_filesystem-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_regex-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_log_setup-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_thread-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_date_time-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_chrono-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_system-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_atomic-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\Xalan-C_1D.lib C:\build\b\stage\lib\xerces-c_3D.lib C:\build\b\tools\lib\gtest.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." LINK Pass 1: command "C:\PROGRA~2\MICROS~1.0\VC\bin\amd64\link.exe /nologo test\ome-files\CMakeFiles\ometiffwriter.dir\ometiffwriter.cpp.obj test\ome-files\CMakeFiles\ometiffwriter.dir\tiffsamples.cpp.obj /out:test\ome-files\ometiffwriter.exe /implib:test\ome-files\ometiffwriter.lib /pdb:test\ome-files\ometiffwriter.pdb /version:0.0 /machine:x64 /debug /INCREMENTAL /subsystem:console lib\ome\files\ome-filesd.lib lib\ome\test\ome-testd.lib C:\build\b\stage\lib\ome-xmld.lib C:\build\b\stage\lib\boost_random-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\tiffd.lib C:\build\b\stage\lib\ome-commond.lib C:\build\b\stage\lib\boost_iostreams-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_log-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_filesystem-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_regex-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_log_setup-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_thread-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_date_time-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_chrono-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_system-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\boost_atomic-vc140-mt-gd-x64-1_67.lib C:\build\b\stage\lib\Xalan-C_1D.lib C:\build\b\stage\lib\xerces-c_3D.lib C:\build\b\tools\lib\gtest.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:test\ome-files\CMakeFiles\ometiffwriter.dir/intermediate.manifest test\ome-files\CMakeFiles\ometiffwriter.dir/manifest.res" failed (exit code 1120) with the following output: Creating library test\ome-files\ometiffwriter.lib and object test\ome-files\ometiffwriter.exp ome-filesd.lib(OMETIFFWriter.cpp.obj) : error LNK2019: unresolved external symbol BCryptCloseAlgorithmProvider referenced in function "public: __cdecl boost::uuids::detail::random_provider_base::~random_provider_base(void)" (??1random_provider_base@detail@uuids@boost@@QEAA@XZ) ome-filesd.lib(OMETIFFWriter.cpp.obj) : error LNK2019: unresolved external symbol BCryptGenRandom referenced in function "public: void __cdecl boost::uuids::detail::random_provider_base::get_random_bytes(void *,unsigned __int64)" (?get_random_bytes@random_provider_base@detail@uuids@boost@@QEAAXPEAX_K@Z) ome-filesd.lib(OMETIFFWriter.cpp.obj) : error LNK2019: unresolved external symbol BCryptOpenAlgorithmProvider referenced in function "public: __cdecl boost::uuids::detail::random_provider_base::random_provider_base(void)" (??0random_provider_base@detail@uuids@boost@@QEAA@XZ) test\ome-files\ometiffwriter.exe : fatal error LNK1120: 3 unresolved externals Looking at boost/winapi/bcrypt.hpp from the 1.67.0 source tar.bz2, I see these symbols prototyped, but not defined anywhere. Is this header broken, missing the implementation? Thanks, Roger

4 4

Seeking help to build GitHub forks on AppVeyor and Travis
by Cromwell Enage 22 Apr '18

22 Apr '18

Hi, all! 1. Is this the right mailing list to seek help for building forks of Boost library modules on GitHub? If not, which mailing list should I bring the next questions to? 2. On my Boost.Parameter fork, one of the AppVeyor jobs gets cut off after 1 hour. How do I split the job into several jobs, one for each compiler or smaller set of compilers? 3. The Boost.MultiArray project on GitHub doesn't have AppVeyor or Travis configuration files, so I created a couple for my fork based on the ones that exist in Boost.Parameter. The AppVeyor jobs error out because they don't recognize the compile-fail rule when running the Jamfile script. Any clues as to what I'm missing? 4. On my Boost.MultiArray fork, one of the Travis jobs builds fine, but the other fails because <boost/array.hpp> is not found. Has anyone else run into this issue? If so, what was your workaround? My GitHub account is GitHub.com/CromwellEnage, in case anyone wants to peruse. Thanks in advance! Cromwell D. Enage

2 2

[graph][graph_parallel][disjoint_sets] Of dependencies and "pending" libraries.
by Rene Rivera 21 Apr '18

21 Apr '18

In the process of creating Conan packages I ran into the rather strange "disjoint_sets" library. It's a library that has been "pending" for 18 years, AFAICT. I don't know what a pending status means for this. But for creating modular packages it means it's a giant PITA to deal with the the interdependencies of "disjoint_sets", "graph", and "graph_parallel". What I want to know is: 1. What is this hidden "disjoint_sets" library/module that only has two headers? 2. Why isn't "disjoint_sets" in the "graph" library tree, especially given that it's not an official library (AFAICT)? 3. Why is "graph_parallel" not in the "graph" library also? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net

3 4

[release] Boost 1.67.0 Release Candidate 2
by Daniel James 20 Apr '18

20 Apr '18

The second release candidates for the 1.67.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.67.0/source/> The SHA256 checksums are as follows: 1cd94f03a71334a67d36f5161b57f5931e0cd6ecf726d7aca8bd82a3be720b74 boost_1_67_0_rc2.7z 2684c972994ee57fc5632e03bf044746f6eb45d4920c343937a465fd67a5adba boost_1_67_0_rc2.tar.bz2 8aa4e330c870ef50a896634c931adf468b21f8a69b77007e45c444151229f665 boost_1_67_0_rc2.tar.gz 7e37372d8cedd0fd6b7529e9dd67c2cb1c60e6c607aed721f5894d704945a7ec boost_1_67_0_rc2.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.

11 12

Bug or change behavior in Fusion at_c in boost 1.66 and 1.67
by Pietro Incardona 18 Apr '18

18 Apr '18

Dear boost developers I used to use boost vector container with arrays like in the code below #include <boost/fusion/sequence/intrinsic/at.hpp> #include <boost/fusion/include/at.hpp> #include <boost/fusion/container/vector.hpp> int main() { boost::fusion::vector<int[3], int, int> v; boost::fusion::at_c<1>(v) = 2; boost::fusion::at_c<0>(v)[0] = 1; //// <----- Broken on newer boost version } Compiled with g++ --std=c++11 -I/home/i-bird/BOOST_166/include -o out main.cpp Unfortunately while this code was working under BOOST 1.63, on Boost 1.66 and Boost 1.67 it does not compile and it produce this error below. It seem that include/boost/fusion/container/vector/detail/value_at_impl.hpp went under some "modernization" process that broke the code above Regards Pietro /////////////////////////// Error ///////////////////////////////////////////// In file included from /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/at_impl.hpp:12:0, from /home/i-bird/BOOST_166/include/boost/fusion/container/vector/vector.hpp:29, from /home/i-bird/BOOST_166/include/boost/fusion/container/vector.hpp:12, from main.cpp:3: /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/value_at_impl.hpp: In instantiation of ‘struct boost::fusion::extension::value_at_impl<boost::fusion::vector_tag>::apply<boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’: /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/at_impl.hpp:45:95: required from ‘struct boost::fusion::extension::at_impl<boost::fusion::vector_tag>::apply<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:66:16: required from ‘struct boost::fusion::detail::at_impl<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0>, boost::fusion::vector_tag>’ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:81:16: required from ‘struct boost::fusion::result_of::at<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:86:16: required from ‘struct boost::fusion::result_of::at_c<const boost::fusion::vector<int [3], int, int>, 0>’ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:127:5: required by substitution of ‘template<int N, class Sequence> constexpr typename boost::fusion::result_of::at_c<const Sequence, N>::type boost::fusion::at_c(const Sequence&) [with int N = 0; Sequence = boost::fusion::vector<int [3], int, int>]’ main.cpp:9:26: required from here /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/value_at_impl.hpp:53:68: error: no matching function for call to ‘value_at_impl<mpl_::int_<0>::value>(boost::fusion::vector<int [3], int, int>*)’ decltype(vector_detail::value_at_impl<N::value>(boost::declval<Sequence*>())) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/value_at_impl.hpp:38:11: note: candidate: template<long unsigned int N, class U> U boost::fusion::vector_detail::value_at_impl(const volatile boost::fusion::vector_detail::store<N, U>*) U value_at_impl(store<N, U> const volatile*); ^~~~~~~~~~~~~ /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/value_at_impl.hpp:38:11: note: template argument deduction/substitution failed: /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/value_at_impl.hpp:53:68: note: template argument ‘1’ does not match ‘0’ decltype(vector_detail::value_at_impl<N::value>(boost::declval<Sequence*>())) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/value_at_impl.hpp:53:68: note: template argument ‘2’ does not match ‘0’ /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/value_at_impl.hpp: In substitution of ‘template<long unsigned int N, class U> U boost::fusion::vector_detail::value_at_impl(const volatile boost::fusion::vector_detail::store<N, U>*) [with long unsigned int N = 0; U = int [3]]’: /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/value_at_impl.hpp:53:68: required from ‘struct boost::fusion::extension::value_at_impl<boost::fusion::vector_tag>::apply<boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/at_impl.hpp:45:95: required from ‘struct boost::fusion::extension::at_impl<boost::fusion::vector_tag>::apply<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:66:16: required from ‘struct boost::fusion::detail::at_impl<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0>, boost::fusion::vector_tag>’ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:81:16: required from ‘struct boost::fusion::result_of::at<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:86:16: required from ‘struct boost::fusion::result_of::at_c<const boost::fusion::vector<int [3], int, int>, 0>’ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:127:5: required by substitution of ‘template<int N, class Sequence> constexpr typename boost::fusion::result_of::at_c<const Sequence, N>::type boost::fusion::at_c(const Sequence&) [with int N = 0; Sequence = boost::fusion::vector<int [3], int, int>]’ main.cpp:9:26: required from here /home/i-bird/BOOST_166/include/boost/fusion/container/vector/detail/value_at_impl.hpp:38:11: error: function returning an array U value_at_impl(store<N, U> const volatile*); ^~~~~~~~~~~~~ main.cpp: In function ‘int main()’: main.cpp:9:26: error: no matching function for call to ‘at_c<0>(boost::fusion::vector<int [3], int, int>&)’ boost::fusion::at_c<0>(v)[0] = 1; ^ In file included from main.cpp:1:0: /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:119:5: note: candidate: template<int N, class Sequence> constexpr typename boost::lazy_disable_if<boost::is_const<Sequence>, boost::fusion::result_of::at_c<Sequence, N> >::type boost::fusion::at_c(Sequence&) at_c(Sequence& seq) ^~~~ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:119:5: note: template argument deduction/substitution failed: /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:127:5: note: candidate: template<int N, class Sequence> constexpr typename boost::fusion::result_of::at_c<const Sequence, N>::type boost::fusion::at_c(const Sequence&) at_c(Sequence const& seq) ^~~~ /home/i-bird/BOOST_166/include/boost/fusion/sequence/intrinsic/at.hpp:127:5: note: substitution of deduced template arguments resulted in errors seen above [i-bird@localhost boost_bug_test]$ [i-bird@localhost boost_bug_test]$ [i-bird@localhost boost_bug_test]$ [i-bird@localhost boost_bug_test]$ g++ --std=c++11 -I/home/i-bird/BOOST_167/include -o out main.cpp In file included from /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/at_impl.hpp:12:0, from /home/i-bird/BOOST_167/include/boost/fusion/container/vector/vector.hpp:29, from /home/i-bird/BOOST_167/include/boost/fusion/container/vector.hpp:12, from main.cpp:3: /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/value_at_impl.hpp: In instantiation of ‘struct boost::fusion::extension::value_at_impl<boost::fusion::vector_tag>::apply<boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’: /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/at_impl.hpp:45:95: required from ‘struct boost::fusion::extension::at_impl<boost::fusion::vector_tag>::apply<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:66:16: required from ‘struct boost::fusion::detail::at_impl<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0>, boost::fusion::vector_tag>’ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:81:16: required from ‘struct boost::fusion::result_of::at<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:86:16: required from ‘struct boost::fusion::result_of::at_c<const boost::fusion::vector<int [3], int, int>, 0>’ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:127:5: required by substitution of ‘template<int N, class Sequence> constexpr typename boost::fusion::result_of::at_c<const Sequence, N>::type boost::fusion::at_c(const Sequence&) [with int N = 0; Sequence = boost::fusion::vector<int [3], int, int>]’ main.cpp:9:26: required from here /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/value_at_impl.hpp:53:68: error: no matching function for call to ‘value_at_impl<mpl_::int_<0>::value>(boost::fusion::vector<int [3], int, int>*)’ decltype(vector_detail::value_at_impl<N::value>(boost::declval<Sequence*>())) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/value_at_impl.hpp:38:11: note: candidate: template<long unsigned int N, class U> U boost::fusion::vector_detail::value_at_impl(const volatile boost::fusion::vector_detail::store<N, U>*) U value_at_impl(store<N, U> const volatile*); ^~~~~~~~~~~~~ /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/value_at_impl.hpp:38:11: note: template argument deduction/substitution failed: /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/value_at_impl.hpp:53:68: note: template argument ‘1’ does not match ‘0’ decltype(vector_detail::value_at_impl<N::value>(boost::declval<Sequence*>())) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/value_at_impl.hpp:53:68: note: template argument ‘2’ does not match ‘0’ /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/value_at_impl.hpp: In substitution of ‘template<long unsigned int N, class U> U boost::fusion::vector_detail::value_at_impl(const volatile boost::fusion::vector_detail::store<N, U>*) [with long unsigned int N = 0; U = int [3]]’: /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/value_at_impl.hpp:53:68: required from ‘struct boost::fusion::extension::value_at_impl<boost::fusion::vector_tag>::apply<boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/at_impl.hpp:45:95: required from ‘struct boost::fusion::extension::at_impl<boost::fusion::vector_tag>::apply<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:66:16: required from ‘struct boost::fusion::detail::at_impl<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0>, boost::fusion::vector_tag>’ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:81:16: required from ‘struct boost::fusion::result_of::at<const boost::fusion::vector<int [3], int, int>, mpl_::int_<0> >’ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:86:16: required from ‘struct boost::fusion::result_of::at_c<const boost::fusion::vector<int [3], int, int>, 0>’ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:127:5: required by substitution of ‘template<int N, class Sequence> constexpr typename boost::fusion::result_of::at_c<const Sequence, N>::type boost::fusion::at_c(const Sequence&) [with int N = 0; Sequence = boost::fusion::vector<int [3], int, int>]’ main.cpp:9:26: required from here /home/i-bird/BOOST_167/include/boost/fusion/container/vector/detail/value_at_impl.hpp:38:11: error: function returning an array U value_at_impl(store<N, U> const volatile*); ^~~~~~~~~~~~~ main.cpp: In function ‘int main()’: main.cpp:9:26: error: no matching function for call to ‘at_c<0>(boost::fusion::vector<int [3], int, int>&)’ boost::fusion::at_c<0>(v)[0] = 1; ^ In file included from main.cpp:1:0: /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:119:5: note: candidate: template<int N, class Sequence> constexpr typename boost::lazy_disable_if<boost::is_const<Sequence>, boost::fusion::result_of::at_c<Sequence, N> >::type boost::fusion::at_c(Sequence&) at_c(Sequence& seq) ^~~~ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:119:5: note: template argument deduction/substitution failed: /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:127:5: note: candidate: template<int N, class Sequence> constexpr typename boost::fusion::result_of::at_c<const Sequence, N>::type boost::fusion::at_c(const Sequence&) at_c(Sequence const& seq) ^~~~ /home/i-bird/BOOST_167/include/boost/fusion/sequence/intrinsic/at.hpp:127:5: note: substitution of deduced template arguments resulted in errors seen above

3 3

Proposal of a new container
by Vanand Gasparyan 16 Apr '18

16 Apr '18

Hi everyone, First, a short introduction of me. My name is Vanand, I'm from Armenia, 23 yo, C++ software Engineer. I'm new in the community and I've come with a proposal. I've implemented a prefix tree and tried to make it as STL compatible as possible. After a short investigation I found out that boost libraries don't provide one and here I am with a proposal. Here is the link to the repository: https://github.com/vgasparyan1995/prefix_tree It's a header only implementation, all source files are in "include" directory. I also have unit and performance tests. If the proposal (of having prefix tree container in boost) is accepted, I will ask for mentorship and support to make it "boost friendly" , create a proper documentation, meet the coding style and other guidelines. In the end I want to mention that I am new to this, so if I'm already doing something wrong or this is not the proper way to propose something, please kindly let me know and help to do it right. Looking forward to hearing from anyone :) Best Regards, Vanand

2 4

[release] 1.68.0 open for merging
by Daniel James 15 Apr '18

15 Apr '18

The master branch is open for merging all stable changes from develop, including bug fixes and major upgrades to existing libraries. Breaking changes should be coordinated via the mailing list with the developers of the other libraries affected. New libraries may be added, but require permission of a release manager. In other words, merging does not require permission from a release manager, except for new libraries. Boost Calendar with the release schedule: http://www.boost.org/development/index.html Release schedule explanation: https://github.com/boostorg/boost/wiki/Release-Schedule Release practices for developers: http://svn.boost.org/trac/boost/wiki/ImprovingPractices -- The Boost Release Team

1 0

[release] Boost 1.67.0
by Daniel James 14 Apr '18

14 Apr '18

Release 1.67.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 2 new libraries and numerous enhancements and bug fixes for existing libraries. For details, including download links, see <https://www.boost.org/users/news/version_1.67.0> You can also download directly from: <https://dl.bintray.com/boostorg/release/1.67.0/> To install this release on your system, see <https://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. Thanks, -- The Boost Release Team

2 1

Library for printing STL containers
by Eric Curtin 14 Apr '18

14 Apr '18

Hi Guys, I have tried to contact the developer of this neat little library. It allows you to use streams such as ostringstreams and couts with various STL containers, without the boilerplate of any loops to get all the contents. I will likely fork and maintain it as I have tried (and failed) to contact the developer. https://github.com/louisdx/cxx-prettyprint If I cleaned it up, could we consider it for boost inclusion? It is already under boost open source license.

2 1

MSVC now correctly reports __cplusplus
by degski 12 Apr '18

12 Apr '18

https://blogs.msdn.microsoft.com/vcblog/2018/04/09/msvc-now-correctly-repor… degski

1 0

[release] Boost 1.67.0 Release Candidate 1
by Daniel James 11 Apr '18

11 Apr '18

The release candidates for the 1.67.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.67.0/source/> The SHA256 checksums are as follows: 289d55fc90b637781018c4babe3ba83244175aa539b54bc687529a65e352e713 boost_1_67_0_rc1.7z 0d13e038f8f402ea0d811397876c8e6f2a2352c170f90d0a42bb61dcec3f86fc boost_1_67_0_rc1.tar.bz2 5d25d1cdf6f7061f25463f59ce2e5c9e1cecfece90d86a04513de386c86fbb5e boost_1_67_0_rc1.tar.gz ae8d461a8573d24813c92e3daf1f7832908d1845820d94b77243d6cd06197635 boost_1_67_0_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.

4 5

[build] Broken doc links
by Gavin Lambert 10 Apr '18

10 Apr '18

Prompted by the thread "Toolset version for Visual Studio 2017 15.6.3" over in the user list, I was looking through some Boost.Build documentation when I found some dead links and other weirdness. Boost.Build's github page links to https://www.boost.org/build/, which appears to be fully working. On https://www.boost.org/doc/libs/1_66_0/more/getting_started/windows.html, under "5.2.1 Install Boost.Build" it links to https://www.boost.org/doc/libs/1_66_0/tools/build/index.html, which appears to be a versioned clone of the above. But at that page, the "Documentation" link points at https://www.boost.org/doc/libs/1_66_0/tools/build/doc/html/index.html, which 404s. Back in "Getting Started", in "5.2.2 Identify Your Toolset" it first links directly to https://www.boost.org/build/doc/html/bbv2/reference/tools.html (which is now an unversioned link, but does work), and then to https://www.boost.org/doc/libs/1_66_0/doc/html/bbv2/installation.html (which is a versioned link that also works). So it's not very consistent. Putting these things together, it looks like the "right" root page for the versioned documentation should be https://www.boost.org/doc/libs/1_66_0/doc/html/bbv2.html, although that lacks some user-friendliness. (And it also links to https://www.boost.org/boost-build2 for yet another URL variation... although that does redirect to https://www.boost.org/build/ at least.)

2 2

please integrate patches for Boost.Gil and Boost.Graph
by Brook Milligan 10 Apr '18

10 Apr '18

I am not sure what the correct procedure for this is, but there are at least two old patches that would improve Boost.Gil and Boost.Graph. I would greatly appreciate it if someone integrates these. I have been using these for some time now with no detrimental effects. The patch to Boost.Gil corrects clearly incorrect code. The patch to Boost.Graph solves a problem that should never have been in the original design in the first place. Since it expands the acceptable set of arguments to cover the full range of values any user would expect and has the original semantics for cases that worked before, as far as I can see there can be no effect on existing user code. Thank you very much. Cheers, Brook See the following: - https://lists.boost.org/Archives/boost/2013/02/200721.php - https://svn.boost.org/trac10/ticket/7270 - https://svn.boost.org/trac10/ticket/9517 - https://svn.boost.org/trac10/attachment/ticket/9517/gil_channel_algorithm.p… - https://svn.boost.org/trac10/ticket/13397 --- boost/gil/channel_algorithm.hpp.orig 2018-02-23 22:45:42.000000000 -0700 +++ boost/gil/channel_algorithm.hpp 2018-03-11 22:05:31.000000000 -0600 @@ -25,6 +25,7 @@ #include "gil_config.hpp" #include "channel.hpp" +#include <limits> #include <boost/mpl/less.hpp> #include <boost/mpl/integral_c.hpp> #include <boost/mpl/greater.hpp> @@ -51,7 +52,7 @@ template <typename UnsignedIntegralChannel> -struct unsigned_integral_max_value : public mpl::integral_c<UnsignedIntegralChannel,-1> {}; +struct unsigned_integral_max_value : public mpl::integral_c<UnsignedIntegralChannel,std::numeric_limits<UnsignedIntegralChannel>::max()> {}; template <> struct unsigned_integral_max_value<uint8_t> : public mpl::integral_c<uint32_t,0xFF> {}; Allow dimensions to have length >= 1, rather than > 1. See https://svn.boost.org/trac10/ticket/11735. --- boost/graph/grid_graph.hpp.orig 2017-12-13 16:56:43.000000000 -0700 +++ boost/graph/grid_graph.hpp 2018-04-07 09:33:56.000000000 -0600 @@ -630,15 +630,17 @@ // If the vertex is on the edge of this dimension, then its // number of out edges is dependent upon whether the dimension - // wraps or not. - if ((vertex[dimension_index] == 0) || - (vertex[dimension_index] == (length(dimension_index) - 1))) { - out_edge_count += (wrapped(dimension_index) ? 2 : 1); - } - else { - // Next and previous edges, regardless or wrapping - out_edge_count += 2; - } + // wraps or not, but only if the length is > 1. + if (length(dimension_index) > 1) { + if ((vertex[dimension_index] == 0) || + (vertex[dimension_index] == (length(dimension_index) - 1))) { + out_edge_count += (wrapped(dimension_index) ? 2 : 1); + } + else { + // Next and previous edges, regardless or wrapping + out_edge_count += 2; + } + } } return (out_edge_count);

4 7

[concept_check] Reference page concept links out-of-date
by Spencer Collyer 09 Apr '18

09 Apr '18

Not sure if this has been reported before, but any links on the Reference page of the concept_check library that point to SGI.com now take you to a page that says 'SGI.com Tech Archive Resources now retired'. Regards, Spencer Collyer

5 4

Reducing dependencies
by Antony Polukhin 08 Apr '18

08 Apr '18

Hello, I've noted that many libraries depend on container_hash while it depends only on a single header from Boost.Detail library https://pdimov.github.io/boostdep-report/master/module-levels.html Can we move "boost/detail/container_fwd.hpp" into Boost.Core or into Boost.ContainerHash? This will break the circular dependency, move the Boost.ContainerHash on level 4 and improve levels of Intrusive, Container, CircularBuffer, Unordered, Algorithm, Test, TypeIndex, Any, Function, Functional, ScopeExit, Signals, MultiArray, Variant. -- Best regards, Antony Polukhin

6 12

[release] 1.67.0 mostly closed for release candidate
by Daniel James 07 Apr '18

07 Apr '18

The master branch is now closed for all changes except by permission for the release candidate. We're expecting potential fixes for build, context and a documentation update for ptr_container. Please let us know if there are any other fixes that you want to include in the release. Thanks, -- The Boost Release Team

5 9

mkmakefile
by Ggh 05 Apr '18

05 Apr '18

Hi! is anyone interested in developing this code further? pls have a look at: http://www.multi.fi/~ghaga http://www.multi.fi/~ghaga/mkmakefile/ anyone? Ty, Greg

4 6

[ptr_container] Docs not updated to reflect std::auto_ptr -> std:unique_ptr changes
by Edward Diener 04 Apr '18

04 Apr '18

An issue was recently created that while ptr_container now supports std::unique_ptr where appropriate and no longer supports std::auto_ptr where it has been removed from the C++ standard, the docs were never updated to reflect this change. I thought it would be worthwhile mentioning this as we go to the 1.67 release. A contributo is preparing a PR to correct this issue, and I will review as a member of CMT once the PR is submitted. I don't mean this as a way to delay the new release but I thought I should bring this up in the mailing list so others know this is the case.

2 1

[1.67] Missing include in Boost.Graph
by Denis Davydov 03 Apr '18

03 Apr '18

Dear all, 1.67.0.beta1 has a regression of missing include in Boost.Graph which prevents deal.II https://www.dealii.org <https://www.dealii.org/> project from building. Even though the file was not modified since 2015, it’s a regression as we have not had this issue with previous versions of boost. The one-liner fix is here https://github.com/boostorg/graph/pull/104 <https://github.com/boostorg/graph/pull/104> I would appreciate if you could merge it prior to 1.67.0 release. ps. https://github.com/boostorg/graph/pull/101 <https://github.com/boostorg/graph/pull/101> is a better way to fix it but as suggested in https://svn.boost.org/trac10/ticket/13505#comment:4 <https://svn.boost.org/trac10/ticket/13505#comment:4> this might not get merged into 1.67.0, which would be pity. Regards, Denis

3 2

Build breaking changes
by Antony Polukhin 03 Apr '18

03 Apr '18

Hello, I've just noted that building Boost from master stopped working: [00:16:51] b2.exe -j4 toolset=gcc --layout=system variant=release architecture=x86 link=static --with-program_options --with-filesystem --with-system --with-test --with-atomic --with-thread --with-timer --with-date_time --with-chrono --with-regex --with-random --with-context stage [00:16:52] Performing configuration checks [00:16:52] [00:16:52] - default address-model : 32-bit [00:16:53] - default architecture : x86 [00:16:53] - symlinks supported : yes (cached) [00:16:54] - C++11 mutex : yes [00:16:55] - has_icu builds : no [00:16:55] - BOOST_COMP_GNUC >= 4.3.0 : yes [00:16:55] - C++11 mutex : no [00:16:56] - has_icu builds : no [00:16:56] - BOOST_COMP_GNUC >= 4.3.0 : no [00:16:56] error: Name clash for '<pstage\lib>libboost_atomic.a' [00:16:56] error: [00:16:56] error: Tried to build the target twice, with property sets having [00:16:56] error: these incompatible properties: [00:16:56] error: [00:16:56] error: - <address-model>64 [00:16:56] error: - <address-model>32 [00:16:56] error: [00:16:56] error: Please make sure to have consistent requirements for these [00:16:56] error: properties everywhere in your project, especially for install [00:16:56] error: targets. [00:16:56] [00:16:56] Command exited with code 1 Previously this build command worked fine. Full log available at https://ci.appveyor.com/project/apolukhin/boost-cookbook/branch/second_edit… Is this an intended breaking change?

12 21

Debate until Decision
by James E. King, III 03 Apr '18

03 Apr '18

I'm going to float some thoughts about how the group makes decisions below. I'm not suggesting a specific course of action, but I would like people to think about how these ideas can be used to improve Boost development. Recent discussions about default address-model, and past discussions about issues like cmake and CI build improvements (like whether or not to purchase more build slaves from travis or appveyor), and topics about legal use of code snippets leads me to the following conclusion: 1. We are geographically, culturally, and vertically distributed and have highly varying viewpoints. 2. We are all very good at expressing our viewpoint about various topics. 3. We collectively need to improve our skill at coming to a group decision and moving forward. Folks generally have individual control over their respective maintained repositories in the current structure. There are many topics that generally affect all of the repositories, such as the ones I mentioned previously, that affect all of us. At my most recent startup company we implemented an effective "Debate until Decision" mechanism by which: 1. The issue is discussed. (We do this well) 2. A decision is made and implemented (We do not seem to do this well): Not everyone will be happy with the outcome. Folks should not attempt to undermine the outcome after decision. The issue can be raised again if new information is brought to light. How is a decision made? Typically in a meeting where people vote face-to-face. For a group like this, voting would be done online with a time limit. Who can vote? That's a good question. In this environment it may fall to the group of folks who are maintainers of an affected repository. I don't necessarily have a good answer for that, as I am relatively new to the group. Some folks have been here for 10+ years and may feel differently that seniority should have a say. I don't know. What are the benefits of this? Simply: *Things get done.* Look at the cmake discussion, or the CI build job discussion, or the current address-model discussion. These need to be finished, agreed to, and implemented (or not), and everyone moves forward. The Apache Software Foundation maintains a fairly well documented structure for each project, with a project management committee consisting of a chair and members who have equal voting rights, however said group's primary function is to identify and grow the team of developers who have commit privileges. The committers as a whole vote on issues that are project-wide, like "should we split into multiple repositories", or "should we move to another source code control environment"? This mechanism could also be applied to how folks are brought into maintainer status for a repository, or how a library enters the CMT. If you look at the bug backlog in trac for some one the libraries, it's pretty clear that they are not properly maintained. The issue may be discussed, but then dropped and forgotten, and no action is taken to remedy it. When repositories have pull requests open for years, or a backlog of 100 defects going back 10 years, there's a very unhealthy problem for that project that needs to be addressed. It may be a similar structure that will work well here. Folks may disagree. This will be debated, certainly, as folks probably have varying opinions about how much structure is needed or desired. I simply hope this leads to an effective discussion about how this group identifies deficiencies, solves them, and moves forward. Any group large or small can benefit from examination and improvement of processes, including ours. Thanks, Jim

5 5