November 2016 - Boost - lists.preview.boost.org

Visual Studio 2015 Update 3 has removed std::unary_function and std::binary_function
by Marshall Clow 12 Nov '16

12 Nov '16

... if you build with /std:c++latest. See https://svn.boost.org/trac/boost/ticket/12586 for an example. Other vendors will be removing these types in C++17 mode in the future (or at least requiring a -D RETAIN_REMOVED_STUFF=1 or something like that) A quick grep for these terms found 153 instances of "std::unary_function" and 118 of "std::binary_function" across several libraries, including accumulators, algorithm, config, container, function, gil, graph, icl, mpi, msm, polygon, ptr_container, serialization, smart_ptr, tr1, unordered, utility - and probably others. I think that we ought to have a boost-wide solution for this (i.e, everyone should solve this the same way). I can think of three possibilities: * Deny, deny, deny: Boost doesn't work with C++17. Not my recommendation. * Since std::unary|binary_function is an empty struct with a set of two (or three) typedefs, just define the typedefs everywhere. Note that the typedefs (result_type, first_argument_type, second_argument_type) were deemed to not be useful in C++17 due to the existence of advanced type traits, etc. * Define a boost:unary_function and boost::binary_function struct that mimics the one that was in namespace std, and change over to use that. * Something else. Comments? -- Marshall

15 74

Adding any_dynamic_cast?
by Peter Dimov 12 Nov '16

12 Nov '16

I stumbled across https://github.com/bytemaster/Boost.DynamicAny which implements, in a fully backward compatible manner, dynamic cast functionality for boost::any. That is, it can give you X* from an 'any' holding a value of type Y if Y derives from X. It achieves this by simply changing template<typename ValueType> class holder : public placeholder { ValueType held; to template<typename ValueType> class holder : public placeholder, public ValueType which then enables dynamic_cast from holder<>* to OtherValueType*. This is pretty cool, and I don't remember seeing this idea anywhere else. Perhaps we should adopt it? One might even argue that this is how any_cast should always have worked, but I suppose we can't change it now for compatibility reasons. Although it's an interesting question whether C++17 'any' shouldn't be enhanced in this manner.

2 2

Request for a new submodule, tools/depinst
by Peter Dimov 12 Nov '16

12 Nov '16

I'd like to request the creation of a new submodule, tools/depinst, that will contain a Python script depinst.py which would, given a module in libs/, install the dependencies needed for running that module's tests. Currently, the .travis.yml files I use enumerate the dependencies manually, which is a bit tiresome: https://github.com/boostorg/function/blob/develop/.travis.yml - git submodule init libs/algorithm - git submodule init libs/align ... - git submodule init libs/type_traits - git submodule init libs/typeof - git submodule init libs/utility - git submodule init libs/winapi - git submodule init tools/build - git submodule update --depth 1 This will be replaced by just - git submodule update --init --depth 1 tools/depinst - git submodule update --init --depth 1 tools/build - python tools/depinst/depinst.py function

5 19

[CI] Activation for Boost.Units
by Jürgen Hunold 11 Nov '16

11 Nov '16

Hi Rene, could you please activate CI via Travis CI and Appveyor for Boost.Units? I hope that I have successfully adapted the scripts from Boost.Predef and that they work for Units as well. Is there any way to get myself some admin rights so I can scheduled cron jobs on TravisCI? I'd like to have at least a weekly run in order to check that no other library break units. And I noticed that the scripts don't work for my fork on GitHub. It needs to detect that and add a remote to the submodule in the Boost checkout somehow. Do you have any plans for that? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

2 1

[Beast] std::to_string not available in gcc 4.8?
by Vinnie Falco 11 Nov '16

11 Nov '16

A user is complaining that std::to_string is not available in their distribution. Beast doesn't support toolchains that don't have full support for C++11. However, if this is the only thing missing maybe I can just use a Boost equivalent to get him up and running. I see boost::to_string in <boost/exception/to_string.hpp> is that a public interface? It doesn't look documented. What do folks typically do when they want to call std::to_string on an unsupported distribution?

4 4

libs/regex/build/Jamfile.v2 missing "import testing"
by Peter Dimov 10 Nov '16

10 Nov '16

In a partial installation (not all submodules installed), running b2 in the Boost root says: libs\regex\build\Jamfile.v2:93: in modules.load ERROR: rule "unit-test" unknown in module "Jamfile<D:\tmp2\boost-root\libs\regex\build>". because libs/regex/build/Jamfile.v2 uses the unit-test rule, defined in testing.jam, but does not have "import testing ;". Adding that line fixes it. I've no idea why it works in a full installation - probably because someone else imports testing first before it gets to regex.

2 1

[process] Formal review results
by Antony Polukhin 09 Nov '16

09 Nov '16

The Boost.Process library is accepted. Congratulations to Klemens, and thanks to everybody who reviewed the library! The votes were as follows: + Johannes - Niall Douglas +/- Tom Kent +/- Nat Goodspeed + Paul A. Bristow +/- Bjorn Reese + Edward Diener + Boris Schäling +/- Raphaël Londeix + Klaim - Joël Lamotte Legend: + accept - decline +/- accept conditionally Separate thanks to Gavin Lambert for providing a solution to deadlocking problem. Additional thanks to Nat Goodspeed, Niall Douglas, Gavin Lambert, Raphaël Londeix and Bjorn Reese for spending significant amount of time on discussing, reviewing or testing the library. -- Quick review summary -- During the review multiple technical issues were raised and as far as I know, Klemens already working on them. The biggest win of the review - is a fix for possible deadlock with pipes. The most controversial part of the library is it's interface. Many comments were addressing: * passing arguments * starting process right in `system(...)` function Current approaches have benefits and drawbacks, other approaches have different benefits and drawbacks. At this point some people agree that the current approach is the lesser evil. Reviewers also wished to have better/richer documentation. P.S.: Please continue with the discussion and report issues that would help to improve the library. -- Best regards, Antony Polukhin

3 3

[dll] trouble building boost dll with Intel compiler on Windows
by Blower, Melanie 09 Nov '16

09 Nov '16

Hello, We are having trouble building boost_dll version 1.61 with Intel compiler (version 17.0) on Windows with vs2015 (and other versions of visual studio). There's a problem because the macro configuration causes alias.hpp to use gnu-like syntax to specify section names: we don't support this syntax in our Windows compiler. Instead, we support "#pragma section" just like the Microsoft compiler. Alias.hpp would use the "correct" configuration for our Windows compiler "#if BOOST_COMP_MSVC" (reference the file boost/dll/alias.hpp) However, the file boost/predef/compiler/visualc.hpp sets BOOST_COMP_MSVC to BOOST_VERSION_NUMBER_ZERO which is 0 I propose that alias.hpp could use BOOST_COMP_MSVC_BUILD instead of BOOST_COMP_MSVC. Does that seem reasonable? Thanks and regards, Melanie Blower (I work for Intel on the Intel C++ compiler)

5 11

[fusion] trouble building boost fusion with Intel compiler on Windows and Linux
by Blower, Melanie 09 Nov '16

09 Nov '16

Hello, We are having trouble building boost_fusion version 1.61 with Intel compiler (version 17.0) on Linux, and on Windows with vs2015 (and other versions of visual studio). The problem can be fixed if I made this change to boost/fusion/container/vector/detail/config.hpp : // Sometimes, MSVC 12 shows compile error with std::size_t of template parameter . #if BOOST_WORKAROUND(BOOST_MSVC, BOOST_TESTED_AT(1800)) \ || BOOST_INTEL /* add this line */ # if defined(BOOST_FUSION_HAS_VARIADIC_VECTOR) # undef BOOST_FUSION_HAS_VARIADIC_VECTOR # endif #endif Symptom on Windows: ile ..\..\..\bin.v2\libs\fusion\test\fold.test\cc848a939769f1f7cf08091b8a228ddb\algorithm\fold.obj.rsp "algorithm\fold.cpp" -Fo"..\..\..\bin.v2\libs\fusion\test\fold.test\cc848a939769f1f7cf08091b8a228ddb\algorithm\fold.obj" -TP /Z7 /Od /Ob0 /W3 /GR /MDd /Zc:forScope /Zc:wchar_t /nologo /Qwn5 /Qwd985 -Qoption,c,--arg_dep_lookup /Qvc14 -Qpchi- /wd4675 /EHs -c -DBOOST_ALL_NO_LIB=1 "-I..\..\.." compile-c-c++ ..\..\..\bin.v2\libs\fusion\test\fold.test\cc848a939769f1f7cf08091b8a228ddb\algorithm\fold.obj icl @"..\..\..\bin.v2\libs\fusion\test\fold.test\cc848a939769f1f7cf08091b8a228ddb\algorithm\fold.obj.rsp" fold.cpp ../../../boost/fusion/container/vector/vector.hpp(71): error: namespace "boost::fusion::vector_detail::result_of" has no member "value_at_c" : boost::is_convertible<Sequence, typename result_of::value_at_c<This, 0>::type> ^ detected during: instantiation of class "boost::fusion::vector_detail::is_convertible_to_first<Sequence, This, <unnamed>> [with Sequence=int, This=boost::fusion::vector<int>, <unnamed>=1]" at line 305 instantiation of "boost::fusion::vector<T...>::vector(U &&...) [with T=<int>, U=<int>]" at line 159 of "algorithm\fold.cpp" Symptom on Linux: The original failure on Linux (zip.test in boost_fusion) "icpc" -c -xc++ -O0 -g -w1 -inline-level=0 -fPIC -m64 -DBOOST_ALL_NO_LIB=1 -I"../../.." -c -o "../../../bin.v2/libs/fusion/test/zip.test/intl-lnx/dbg/algorithm/zip.o" "algorithm/zip.cpp" ../../../boost/fusion/container/vector/vector.hpp(230): error: pack "U" does not have the same number of elements as "I" : store<I, T>(std::forward<U>(var))... ^ detected during: instantiation of "boost::fusion::vector_detail::vector_data<boost::fusion::detail::index_sequence<I...>, T...>::vector_data(boost::fusion::vector_detail::each_elem, U &&...) [with I=<0UL, 1UL>, T=<boost::fusion::vector_iterator<const boost::fusion::vector<int, int>, 0>, boost::fusion::vector_iterator<const boost::fusion::vector<char, char>, 0>>, U=<const boost::fusion::transform_view<const boost::fusion::vector<const boost::fusion::vector<int, int> &, const boost::fusion::vector<char, char> &>, boost::fusion::detail::poly_begin, boost::fusion::void_> &>]" at line 306 instantiation of "boost::fusion::vector<T...>::vector(U &&...) [with T=<boost::fusion::vector_iterator<const boost::fusion::vector<int, int>, 0>, boost::fusion::vector_iterator<const boost::fusion::vector<char, char>, 0>>, U=<const boost::fusion::transform_view<const boost::fusion::vector<const boost::fusion::vector<int, int> &, const boost::fusion::vector<char, char> &>, boost::fusion::detail::poly_begin, boost::fusion::void_> &>]" at line 41 of "../../../boost/fusion/view/zip_view/zip_view_iterator.hpp" Thanks and regards, Melanie Blower (I work for Intel on the Intel C++ compiler)

3 4

test: Initializiation of data test cases
by Florian Lindner 09 Nov '16

09 Nov '16

Hello, I would like to use data test cases. The problem that comes with that, is that I want to use objects that needs the application to be initialized before they are instantiated. Example is that an object that uses MPI needs to habe MPI_Init called before. This example code shows the order in which different hooks are run: #define BOOST_TEST_DYN_LINK // #define BOOST_TEST_MAIN #include <boost/test/unit_test.hpp> #include <boost/test/data/test_case.hpp> #include <boost/test/data/monomorphic.hpp> #include <mpi.h> #include <iostream> #include <string> #include <vector> using namespace std; struct GlobalFixture { GlobalFixture() { cout << "GlobalFixture" << endl; } ~GlobalFixture() { } }; BOOST_GLOBAL_FIXTURE(GlobalFixture); struct Test : public std::string { // derive from string to get operator<< that boost requires Test() { cout << "Object to test" << endl; } }; namespace bdata = boost::unit_test::data; template <class T> class RuntimeDataset { public: using sample = typename T::value_type;; enum { arity = 1 }; T data; explicit RuntimeDataset(T _data) { cout << "Dataset constructor" << endl; data = _data; } bdata::size_t size() const { return data.size(); } typename T::const_iterator begin() const { return data.cbegin(); } }; namespace boost { namespace unit_test { namespace data { namespace monomorphic { template <class T> struct is_dataset<RuntimeDataset<T>> : boost::mpl::true_ {}; }}}} struct Fixture { Fixture() { cout << "Fixture" << endl; } }; BOOST_AUTO_TEST_SUITE(MySuite) BOOST_DATA_TEST_CASE_F( Fixture, test1, RuntimeDataset<std::vector<Test>>( { Test() } ), // This should be evaluated when the test is about to run input) { BOOST_TEST(true); cout << "Data test case" << endl; } BOOST_AUTO_TEST_SUITE_END() // initialization function: bool init_unit_test() { cout << "init_unit_test" << endl; return true; } // entry point: int main(int argc, char* argv[]) { cout << "main" << endl; int retCode = boost::unit_test::unit_test_main( &init_unit_test, argc, argv ); return retCode; } I've removed some code parts, but it should compile right away using mpic++ -std=c++11 -lboost_unit_test_framework boosttesting.cpp Its output is Object to test Dataset constructor main init_unit_test GlobalFixture Running 1 test case... Fixture Data test case *** No errors detected So, before I have any chance to do my own initialization code, the Test object and the dataset is constructed. I have posted this to the user mailing list, but still looking for a way to work around that. Do you have any idea how I can do initialization before data is instantiated? Thanks, Florian

1 0