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

[interprocess] Determine size of managed_shared_memory
by Kai Benndorf 12 Oct '19

12 Oct '19

Hi all, I want to create a managed_shared_memory in exactly the size I needed. Therefore I do something like this: size = sizeof( common_managed_shared_memory ); size += sizeof( MyClassInSharedMem ); managed_shared_memory segment(create_only, "name", size ); MyClassInSharedMem allocates itself some memory by segment->allocate(). I added this also to the size, but get a boost::interprocess::bad_alloc exception on allocating this additional memory. Are there some magic bytes I forgot to add? Many thanks in advance Kai

3 2

Weird compilation error when using boost::geometry
by 邓尧 16 Nov '17

16 Nov '17

Hi, I have implemented my own "point" as specified by the point concept http://www.boost.org/doc/libs/1_59_0/libs/geometry/doc/html/geometry/refere… When I use it along with boost::geometry::model::polygon/multi_polygon, GCC refuses to compile, tested on GCC 4.9/5.2. What's even more weird is that CLANG 3.6 would happy accept my code. BTW, the Point implementation is part of a large project, it difficult to replace it with boost::geometry::model::point. Here is my code: Point.hpp > #ifndef RAPTOR_POINT_HPP_INCLUDED_ > > #define RAPTOR_POINT_HPP_INCLUDED_ > > >> #include <boost/mpl/int.hpp> > > #include <boost/geometry/core/access.hpp> > > #include <boost/geometry/core/cs.hpp> > > #include <boost/geometry/core/coordinate_type.hpp> > > #include <boost/geometry/core/coordinate_system.hpp> > > #include <boost/geometry/core/coordinate_dimension.hpp> > > #include <boost/geometry/geometries/polygon.hpp> > > #include <boost/geometry/multi/geometries/multi_polygon.hpp> > > >> namespace raptor { > > >> template<typename T, int tDimension = 2> > > class Point { > > public: > > Point() = default; > > >> Point(T a, T b) { > > data[0] = a; > > data[1] = b; > > } > > >> Point(T a, T b, T c) { > > data[0] = a; > > data[1] = b; > > data[2] = c; > > } > > >> T& operator [] (long index) { > > return data[index]; > > } > > >> const T& operator [] (long index) const { > > return data[index]; > > } > > >> private: > > T data[tDimension]; > > }; > > >> using CubicPoint = Point<long, 3>; > > using PlanarPoint = Point<long>; > > using SphericalPoint = Point<double>; > > >> template<typename T> > > using Polygon = boost::geometry::model::polygon<T>; > > >> template<typename T> > > using PolySet = boost::geometry::model::multi_polygon<Polygon<T>>; > > >> } // namespace raptor > > >> namespace boost { namespace geometry { namespace traits { > > >> template<typename Type, std::size_t tDimension> > > struct tag<::raptor::Point<Type, tDimension>> { > > typedef point_tag type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct coordinate_type<::raptor::Point<Type, tDimension>> { > > typedef Type type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct coordinate_system<::raptor::Point<Type, tDimension>> { > > typedef boost::geometry::cs::cartesian type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct dimension<::raptor::Point<Type, tDimension>> > > : public boost::mpl::int_<tDimension> { > > // EMPTY > > }; > > >> template<typename Type, std::size_t tDimension, std::size_t tIndex> > > struct access<::raptor::Point<Type, tDimension>, tIndex> { > > static Type get(const ::raptor::Point<Type, tDimension>& p) { > > return p[tIndex]; > > } > > >> static void set(::raptor::Point<Type, tDimension>& p, > > const Type& value) { > > p[tIndex] = value; > > } > > }; > > >> }}} // namespace boost::geometry::traits > > >> #endif // RAPTOR_POINT_HPP_INCLUDED_ > > A real simple main.cpp: > #include "Point.hpp" > > >> int main() { > > raptor::Polygon<raptor::SphericalPoint> pl; > > raptor::PolySet<raptor::SphericalPoint> set; > > return sizeof(pl) + sizeof(set); > > } > > > GCC compilation error: g++ main.cpp -std=c++14 > In file included from /usr/include/boost/geometry/core/access.hpp:20:0, from Point.hpp:5, from main.cpp:1: /usr/include/boost/geometry/core/point_type.hpp: In instantiation of > 'struct boost::geometry::traits::point_type<raptor::Point<double> >': /usr/include/boost/geometry/core/point_type.hpp:66:17: required from > 'struct boost::geometry::core_dispatch::point_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:58:62: required from > 'struct boost::geometry::core_dispatch::coordinate_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:92:25: required from > 'struct boost::geometry::coordinate_type<raptor::Point<double> >' /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:90:54: > required from 'class boost::geometry::concept::Point<raptor::Point<double> > >' /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/core/point_type.hpp:45:5: error: no matching > function for call to 'assertion_failed(mpl_::failed************ > (boost::geometry::traits::point_type<raptor::Point<double> > >::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE::************)(mpl_::assert_::types<raptor::Point<double>, > mpl_::na, mpl_::na, mpl_::na>))' BOOST_MPL_ASSERT_MSG ^ /usr/include/boost/mpl/assert.hpp:82:5: note: candidate: template<bool C> > int mpl_::assertion_failed(typename mpl_::assert<C>::type) int assertion_failed( typename assert<C>::type ); ^ /usr/include/boost/mpl/assert.hpp:82:5: note: template argument > deduction/substitution failed: /usr/include/boost/geometry/core/point_type.hpp:45:5: note: cannot > convert > 'boost::geometry::traits::point_type<Geometry>::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE48::assert_arg<raptor::Point<double> > >()' (type 'mpl_::failed************ > (boost::geometry::traits::point_type<raptor::Point<double> > >::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE::************)(mpl_::assert_::types<raptor::Point<double>, > mpl_::na, mpl_::na, mpl_::na>)') to type 'mpl_::assert<false>::type {aka > mpl_::assert<false>}' BOOST_MPL_ASSERT_MSG ^ In file included from > /usr/include/boost/geometry/core/coordinate_type.hpp:21:0, from /usr/include/boost/geometry/core/access.hpp:24, from Point.hpp:5, from main.cpp:1: /usr/include/boost/geometry/core/point_type.hpp: In instantiation of > 'struct boost::geometry::core_dispatch::point_type<void, > raptor::Point<double> >': /usr/include/boost/geometry/core/coordinate_type.hpp:58:62: required from > 'struct boost::geometry::core_dispatch::coordinate_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:92:25: required from > 'struct boost::geometry::coordinate_type<raptor::Point<double> >' /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:90:54: > required from 'class boost::geometry::concept::Point<raptor::Point<double> > >' /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/core/point_type.hpp:66:17: error: no type named > 'type' in 'struct boost::geometry::traits::point_type<raptor::Point<double> > >' >::type type; ^ In file included from > /usr/include/boost/geometry/geometries/polygon.hpp:26:0, from Point.hpp:10, from main.cpp:1: /usr/include/boost/geometry/geometries/concepts/point_concept.hpp: In > instantiation of 'class > boost::geometry::concept::Point<raptor::Point<double> >': /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:93:10: > error: 'value' is not a member of > 'boost::geometry::dimension<raptor::Point<double> >' enum { ccount = dimension<Geometry>::value }; ^ Where is the problem ? or it's a GCC bug ? Thanks

3 4

NEWBIE: Undefined references: How do I find the library that resolves an undefined reference
by JENNINGS, LYNN M NH-03 USAF AFMC 517 SMXS/MXDPB 30 May '17

30 May '17

NEWBIE question: Undefined references: How do I find the library that resolves an undefined reference. For example, the output for the gcc linker running in MinGW shows: C:/boost/boost/asio/detail/impl/winsock_init.ipp:39: Undefined reference to `WSAStartup@8' I have googled the documentation a number of ways, but I cannot find the library that will resolve this error. I am sure that this is a common problem. Please point me to the documentation so I can fix this and the undefined references. Thanks!

4 3

Help with Boost Serialization library!
by Alam, Tina 02 May '17

02 May '17

Hi Boost Users, I need the Boost Serialization Library in order to use a MATLAB make file. The make file is looking for a static library file named either boost_serialization.lib or libboost_serialization.lib. However, when I built the serialization library, I got a lot of object files and rsp files rather than a .lib file. Do you know how to create the .lib file? I am not sure if it matters, but I am using a Windows computer. When you build the boost libraries, is there a way to generate .lib files for them? Below, I have documented the steps I took to build the library. Please take a glance at it and let me know if I missed something that will allow me to obtain the .lib file. 1. Download and unzip the boost folder http://www.boost.org/users/history/version_1_63_0.html 1. Look inside folder and make sure you find bootstrap.bat 1. Open the Visual Studio Developer Command Prompt and navigate to the boost folder [cid:image001.jpg@01D2BF3C.88D418B0] 1. Type bootstrap into the command line and hit enter [cid:image002.jpg@01D2BF3C.88D418B0] 1. After it finishes bootstrapping, type in .\b2 --with-serialization and hit enter. The serialization library will be built. I still have not figured out how to generate the .lib file. [cid:image003.jpg@01D2BF3C.88D418B0] Tina Alam IT Flex - Software Engineer

2 1

[review] Review of PolyCollection will start in a few days
by Ion Gaztañaga 30 Apr '17

30 Apr '17

Dear Boost community, The formal review of Joaquín M López Muñoz's PolyCollection library will start on Wednesday, May 3rd and ends on May 12th. This library implements fast containers of polymorphic objects. Typically, polymorphic objects cannot be stored directly in regular containers and need be accessed through an indirection pointer, which introduces performance problems related to CPU caching and branch prediction. Boost.PolyCollection implements a novel data structure that is able to contiguously store polymorphic objects without such indirection, thus providing a value-semantics user interface and better performance. Three polymorphic collections are provided: * boost::base_collection * boost::function_collection * boost::any_collection dealing respectively with classic base/derived or OOP polymorphism, function wrapping in the spirit of std::function and so-called duck typing as implemented by Boost.TypeErasure. If you are interested, you can start preparing your review with the following information: Repositories: Incubator: http://blincubator.com/bi_library/polycollection/?gform_post_id=1643 Github: https://github.com/joaquintides/poly_collection and the documentation here: http://rawgit.com/joaquintides/poly_collection/website/doc/html/index.html See you on Wednesday! Ion

1 0

Fwd: [boost] [clang] clang-cl expansion of macros
by degski 29 Apr '17

29 Apr '17

On 16 April 2016 at 17:58, Edward Diener <eldiener(a)tropicsoft.com> wrote: > What I strongly suspect will finally happen is that clang will not fix > these emulation problems because they are too tricky and numerous to do. > Instead they will probably declare that their emulation is good enough for > the majority of preprocessor constructs and that Boost PP, which pushes the > preprocessor to its limits, is not meant to work with their flawed VC++ > emulation. I hope I am wrong about that supposition, but having spent much > time in Boost PP and Boost VMD trying to workaround VC++ non-standard > preprocessor behavior I can envision that having to code "down" to that > behavior in numerous complicated instances will be too much time consuming > work for the clang developers who have chosen to work with VC++ > preprocessor emulation. > I've successfully built boost-1.64 with VC1410 (from the developer command prompt). Trying to use boost with a project using Clang 4.0.0 (both the LLVM and C2 backends) gives me the following PP error messages: 1>------ Rebuild All started: Project: test, Configuration: Debug x64 ------ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/ iterator/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/ aux_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(59,7): error : too many arguments provided to function-like macro invocation 1> 2 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/ iterator/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/ aux_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(58,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC2( 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(166,44): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC2' 1> #define BOOST_MPL_AUX_NA_SPEC2(i, j, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/ iterator/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/ aux_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(58,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(166,44): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC2' 1> #define BOOST_MPL_AUX_NA_SPEC2(i, j, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/def_params_tail.hpp(97,5): note: expanded from macro 'BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL' 1> BOOST_MPL_PP_DEF_PARAMS_TAIL_IMPL(i, param, BOOST_PP_IDENTITY(=value)) \ 1> ^ 1> note: (skipping 2 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(8,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/ iterator/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/ aux_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(58,1): error : template argument for template type parameter must be a type 1> BOOST_MPL_AUX_NA_SPEC2( 1> ^~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(166,44): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC2' 1> #define BOOST_MPL_AUX_NA_SPEC2(i, j, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(68,17): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> : name< BOOST_MPL_PP_PARAMS(i, T) > \ 1> ^~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> note: (skipping 5 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^~~~~~ 1> <scratch space>(33,1): note: expanded from here 1> T2 1> ^~ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(32,37): note: expanded from macro 'BOOST_PP_CAT_II' 1> # define BOOST_PP_CAT_II(p, res) res 1> ^~~ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(45,39): note: template parameter is declared here 1> , typename BOOST_MPL_AUX_NA_PARAM(T2) 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1> In file included from z:\vc\x64\include\boost/mpl/eval_if.hpp:17: 1>z:\vc\x64\include\boost/mpl/if.hpp(131,23): error : too many arguments provided to function-like macro invocation 1> BOOST_MPL_AUX_NA_SPEC(3, if_) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1> In file included from z:\vc\x64\include\boost/mpl/eval_if.hpp:17: 1>z:\vc\x64\include\boost/mpl/if.hpp(131,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC(3, if_) 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1> In file included from z:\vc\x64\include\boost/mpl/eval_if.hpp:17: 1>z:\vc\x64\include\boost/mpl/if.hpp(131,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> note: (skipping 3 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(4,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1> In file included from z:\vc\x64\include\boost/mpl/eval_if.hpp:17: 1>z:\vc\x64\include\boost/mpl/if.hpp(131,1): error : template argument for template type parameter must be a type 1> BOOST_MPL_AUX_NA_SPEC(3, if_) 1> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(68,17): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> : name< BOOST_MPL_PP_PARAMS(i, T) > \ 1> ^~~~~~~~~~~~~~~~~~~~~~~~~ 1> note: (skipping 6 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^~~~~~ 1> <scratch space>(29,1): note: expanded from here 1> T3 1> ^~ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(32,37): note: expanded from macro 'BOOST_PP_CAT_II' 1> # define BOOST_PP_CAT_II(p, res) res 1> ^~~ 1> z:\vc\x64\include\boost/mpl/if.hpp(53,39): note: template parameter is declared here 1> , typename BOOST_MPL_AUX_NA_PARAM(T3) 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1>z:\vc\x64\include\boost/mpl/eval_if.hpp(67,23): error : too many arguments provided to function-like macro invocation 1> BOOST_MPL_AUX_NA_SPEC(3, eval_if) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1>z:\vc\x64\include\boost/mpl/eval_if.hpp(67,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC(3, eval_if) 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1>z:\vc\x64\include\boost/mpl/eval_if.hpp(67,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> note: (skipping 3 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(29,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1>z:\vc\x64\include\boost/mpl/eval_if.hpp(67,1): error : template argument for template type parameter must be a type 1> BOOST_MPL_AUX_NA_SPEC(3, eval_if) 1> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(68,17): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> : name< BOOST_MPL_PP_PARAMS(i, T) > \ 1> ^~~~~~~~~~~~~~~~~~~~~~~~~ 1> note: (skipping 6 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^~~~~~ 1> <scratch space>(32,1): note: expanded from here 1> T3 1> ^~ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(32,37): note: expanded from macro 'BOOST_PP_CAT_II' 1> # define BOOST_PP_CAT_II(p, res) res 1> ^~~ 1> z:\vc\x64\include\boost/mpl/eval_if.hpp(29,39): note: template parameter is declared here 1> , typename BOOST_MPL_AUX_NA_PARAM(F2) 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(40,30): error : too many arguments provided to function-like macro invocation 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, identity) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(40,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, identity) 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(40,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/def_params_tail.hpp(97,5): note: expanded from macro 'BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL' 1> BOOST_MPL_PP_DEF_PARAMS_TAIL_IMPL(i, param, BOOST_PP_IDENTITY(=value)) \ 1> ^ 1> note: (skipping 2 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(32,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(40,1): error : template argument for template type parameter must be a type 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, identity) 1> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(68,17): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> : name< BOOST_MPL_PP_PARAMS(i, T) > \ 1> ^~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> note: (skipping 5 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^~~~~~ 1> <scratch space>(32,1): note: expanded from here 1> T1 1> ^~ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(32,37): note: expanded from macro 'BOOST_PP_CAT_II' 1> # define BOOST_PP_CAT_II(p, res) res 1> ^~~ 1> z:\vc\x64\include\boost/mpl/identity.hpp(23,39): note: template parameter is declared here 1> typename BOOST_MPL_AUX_NA_PARAM(T) 1> ^ 1>z:\vc\x64\include\boost/mpl/identity.hpp(41,30): error : too many arguments provided to function-like macro invocation 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, make_identity) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(41,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, make_identity) 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(41,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/def_params_tail.hpp(97,5): note: expanded from macro 'BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL' 1> BOOST_MPL_PP_DEF_PARAMS_TAIL_IMPL(i, param, BOOST_PP_IDENTITY(=value)) \ 1> ^ 1> note: (skipping 2 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(61,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1>CL : fatal error : too many errors emitted, stopping now [-ferror-limit=] 1> 20 errors generated. ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ========== Up till now I was using a hacked boost-1.62. So in order to see what would happen, I also built boost-1.63. Apart from a small change in type_with_alignment.hpp (adding a ckeck for _MSC_VER not to exist if __clang__ does exist in line 87), boost-1.63 compiles without a problem (no specific (relevant to the emulation) command line parameters). Is there a macro I should define or is there something else I should set/do in order to use boost-1.64 with Clang 4.0.0 on windows? Any other suggestions? degski -- "*Ihre sogenannte Religion wirkt bloß wie ein Opiat reizend, betäubend, Schmerzen aus Schwäche stillend.*" - Novalis 1798

1 1

[Range, Phoenix] What am I missing...
by Robert Jones 25 Apr '17

25 Apr '17

Hi Folks Can anyone explain the output of this program... #include <iostream> #include <boost/range/algorithm/copy.hpp> #include <boost/range/counting_range.hpp> #include <boost/range/adaptor/reversed.hpp> #include <boost/range/adaptor/transformed.hpp> #include <boost/phoenix/bind/bind_function.hpp> #include <boost/phoenix/core/argument.hpp> int f( int i ) { return i * 2; } int main( ) { using boost::adaptors::reversed; using boost::adaptors::transformed; using boost::counting_range; using boost::copy; using boost::phoenix::arg_names::_1; copy( counting_range( 1, 5 ) | reversed | transformed( f ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; copy( counting_range( 1, 5 ) | reversed | transformed( bind( f, _1 ) ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; } Which is... 8 6 4 2 1768406272 1768406272 1768406272 1768406272 I'm using Gcc 4.6.2 & Boost 1.53 Thx All.

3 4

[Serialization] issue with "Assertion `__null != bpos' failed"
by Francois Mauger 24 Apr '17

24 Apr '17

Hi Robert, all, In some of our libs, we use serialization through a base pointer: We have a base (abstract) class "a::base" which is available from a shared library "liba". We have created a new class "b::foo", inherited from "a::base", hosted in another shared lib "libb", "libb" being explicitly linked to "liba". In "libb", class "b::foo" is exported through : BOOST_CLASS_EXPORT_KEY2(b::foo,"b::foo") (in header foo.hpp) BOOST_CLASS_EXPORT_IMPLEMENT(b::foo) (in some libb's foo-serial.cpp source file) which I think is the right way to process to register a class in a compilation unit. In a test program, I (de)serialize 'b::foo' instances through a 'a::base' pointer. This mechanism has worked for years in all of our software chains. And today it works with our current production software system (ubuntu linux 16.04, g++ 5.4.0, GNU ld 2.26.1, Boost 1.60). However, we now face a runtime error on *some* of our boxes. The message is: <pre> ...test_app...: /path/to/boost/install/include/boost/archive/detail/oserializer.hpp:436: static void boost::archive::detail::save_pointer_type<Archive>::polymorphic::save(Archive&, T&) [ with T = a::base; Archive = boost::archive::xml_oarchive]: Assertion `__null != bpos' failed. Abort (core dumped) </pre> This error only occurs with XML or txt archives, but works like a charm with Christian's EOS portable binary ars. What is strange is that the code works on some of our systems but failed on other ones with the same compiler/linker/boost versions. The exception suggests some problem with class registration but I don't understand this (apparently) arbitrary behaviour. If any of you have a hint to help us to find the solution, it would be appreciated. thanks regards -- François

1 0

really dumb question about quickbook
by Robert Ramey 21 Apr '17

21 Apr '17

I'm struggling with quickbook When I use the following [section:userapi User API] [include types/File.qbk] [include types/Hasher.qbk] [include types/Progress.qbk] [endsect] I don't the files included. But when I use [section:userapi User API] [include types/File.qbk] [include types/Hasher.qbk] [include types/Progress.qbk] [endsect] The other files ARE included. I've looked through the quickbook docs and for the life of me I can't find where the significance (if there is any) of spaces in the markup is explained. Could someone point me in the right direction? Robert Ramey

4 18

[Boost-CRC] Warnings in crc_32_type
by tamas.ruszkai＠leica-geosystems.com 21 Apr '17

21 Apr '17

1 0

[release] Boost 1.64.0
by Rene Rivera 20 Apr '17

20 Apr '17

Release 1.64.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 one new library and numerous enhancements and bug fixes for existing libraries. For details, including download links, see < http://www.boost.org/users/history/version_1_64_0.html> You can also download directly from: < https://dl.bintray.com/boostorg/release/1.64.0/> To install this release on your system, see < http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. Thanks, -- The Boost Release Team Vladimir Prus, Rene Rivera, Marshall Clow, Eric Niebler, Daniel James, Beman Dawes

3 2

[hana] create aribtrary tuples of integral_constants
by Steve Lorimer 19 Apr '17

19 Apr '17

Making use of Scott Schurr's str_const ( https://github.com/boostcon/cppnow_presentations_2012/blob/master/wed/schur…) I have a constexpr string. class StrConst { public: template<size_t N> constexpr StrConst(const char (&str)[N]) : str_(str) , len_(N - 1) { static_assert(N > 1, "not a string"); } constexpr operator const char*() const { return str_; } constexpr size_t size() const { return len_; } constexpr char operator[] (size_t i) const { return i < len_ ? str_[i] : throw std::out_of_range("invalid index"); } private: const char* const str_; const size_t len_; }; I have another constexpr function which returns the position of the first caret found in a string, starting from position n: constexpr int caretPos(const StrConst& str, size_t n = 0) { if (n == str.size()) return -1; if (str[n] == '^') return n; return caretPos(str, n+1); } I can use the results of caretPos to create a typedef for a std::tuple of std::integral_constants, where the size of the tuple is the number of carets found in the string, and each tuple element is an integral constant whose value is the position of the caret in the string. Here I manually construct this tuple: int main() { constexpr StrConst s("hello^world^"); constexpr int pos1 = caretPos(s); constexpr int pos2 = caretPos(s, pos1+1); using P1 = std::integral_constant<int, pos1>; using P2 = std::integral_constant<int, pos2>; using PosTuple = std::tuple<P1, P2>; static_assert(std::tuple_element_t<0, PosTuple>::value == 5, ""); static_assert(std::tuple_element_t<1, PosTuple>::value == 11, ""); } Question: I would now like to generalise this for any input string with any number of carets. template<size_t... Ns> using PosTuple = std::tuple<std::integral_constant<int, Ns>...>; How can I generate the sequence of Ns... required here using caretPos or some other means?

2 1

[release] Boost 1.64.0 Release Candidate 1
by Rene Rivera 17 Apr '17

17 Apr '17

The release candidates for the 1.64.0 release are now available at: <https://dl.bintray.com/boostorg/beta/1.64.0.rc.1/> The SHA256 checksums are as follows: 49c6abfeb5b480f6a86119c0d57235966b4690ee6ff9e6401ee868244808d155 boost_1_64_0_rc1.7z 7bcc5caace97baa948931d712ea5f37038dbb1c5d89b43ad4def4ed7cb683332 boost_1_64_0_rc1.tar.bz2 0445c22a5ef3bd69f5dfb48354978421a85ab395254a26b1ffb0aa1bfd63a108 boost_1_64_0_rc1.tar.gz b99973c805f38b549dbeaf88701c0abeff8b0e8eaa4066df47cac10a32097523 boost_1_64_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. -- The Boost Release Team -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 1

Serialization support for colony container
by Brian Wood 17 Apr '17

17 Apr '17

Shalom It's looking like Matthew Bentley's colony container -- http://plflib.org -- is going to pass over Boost on it's way to the standard. I've added serialization support for this container to the C++ Middleware Writer and added some code that tests that support to my repo -- https://bitbucket.org/webenezer/onwards . I enjoyed Jon Kalb's CppChat show where he talked to Matthew about this container -- http://www.slashslash.info/cppchat/ https://www.youtube.com/watch?v=SFAJ238rBNw -- Brian Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

2 1

[CallableTraits] Review results
by Louis Dionne 17 Apr '17

17 Apr '17

Dear Boost, I am pleased to announce that the CallableTraits library is CONDITIONALLY ACCEPTED into Boost. I counted the following formal reviews: - Bruno Dutra: Yes - Emil Dotchevski: Yes - John P. Fletcher: Yes - Klemens Morgenstern: Yes - Peter Dimov: Yes - Zach Laine: Yes The following people also participated to the review by providing informal feedback: - Edward Diener - Gavin Lambert - Niall Douglas - Paul Fultz II - Tim Song I also based my decision on previous experience I've had using the library, and some issues we faced in the Standard Committee where we could have used CallableTraits. I'd like to thank everyone who participated to the review for their feedback, and also Barrett Adair for his submission. The following lists the conditions for acceptance, and also summarizes the general feedback received during the review. GitHub issues are leveraged to make the tracking of these comments easier. Below, whenever I refer to #XYZ, the corresponding ticket can be found at https://github.com/badair/callable_traits/issues/XYZ To see all the issues that were discussed during the review, you can search for tickets labeled with `review` on GitHub (please allow some time for Barrett to update the new issues I just filed): https://github.com/badair/callable_traits/issues?page=1&q=+label%3Areview Conditions for acceptance ------------------------- The following are points that must be addressed for the library to be accepted. Once all of the associated GitHub issues are closed, I ask that the author post to this list with links to the closed issues. Unless major problems (having to do with the closed issues) are raised at that time, the library will be automatically accepted into Boost, no additional review required. - The library needs to clearly document the advantages of CallableTraits over FunctionTypes. Concrete examples must be given (at least one, preferably two). See #117. - The level of C++ conformance required for the whole library needs to be clearly stated in the documentation. Individual components should only document divergences from that base level of conformance. The current state of things is quite confusing for users. See #118. - The "algorithmic" parts of the library must be removed, since they are out of scope. This has already been partly done in issue #114, but the following algorithms must be discussed too (let's follow up in #114): + args_at + clear_args + pop_front_args + push_front_args + expand_args_right + expand_args_left - The lazy metafunctions and predicate traits should be SFINAE-friendly, just like the aliases are. I think this inconsistency is a big deal, enough to be a condition for acceptance. See #134. Summary of the feedback received -------------------------------- The following is a compilation of other points that were made during the review, but which are not requirements for acceptance. I trust, but do not require, that all of those points will be considered by the author: - There is a loss of information with the `args` metafunction. For example, `void(T)` and `void(T, ...)` both give the same result. See #132. - Consider adding a way of obtaining the parameter list of a function without the type of `*this`. See #133. - The documentation uses the terms of art "implementation defined" and "undefined behavior" incorrectly. See #103 and #131. - The non-reference documentation should present at least one real-world use case. See #116. - The library should handle top-level cv-qualifiers. See #106. - Consider supporting different calling conventions (e.g. `__cdecl`). See #102. - Consider adding a pre-C++17 implementation of `is_invocable` and friends. See #119. - The documentation should clearly state that the library can be used without the rest of Boost. See #99. - Consider combining `expand_args` and `args` into a single metafunction with a default "output" parameter of `std::tuple`. See #126. - Consider adding `make_fn` and `make_mem_fn` metafunctions to construct a signature from a return type and a tuple of the arguments. See #113. - Consider renaming some traits, like `is_reference_member`. See #108. - Reword some parts of the documentation that look odd due to the use of passive tense. See #105. - Consider adding a version of `apply_member_pointer` which carries cv-qualifiers. See #138. - Consider adding `remove_member_cv_ref` and `copy_member_cv_ref`. See #139. - Why does `qualified_parent_class_of` always returns a const& for PMDs? See #112. - Why does `qualified_parent_class_of` return a ref-qualified type even for unqualified PMFs? See #112. A few of my own comments: - Consider using alphabetical order in the table of contents of the reference. See #135. - Consider renaming `apply_member_pointer` to something like `make_member`. See #136. - Consider dropping the `parent_` in `parent_class_of`, or adding a note to justify the name. See #137. Again, thanks to everyone who participated in the review, and congratulations to Barrett for his work! Regards, Louis Dionne

1 0

How to setup log directory in an directory that is not fixed?
by Bruce 17 Apr '17

17 Apr '17

Hi, I am using boost.Log. I config the log using a logconfig.ini file. Now the requirement changed, we need to put the log in an directory specific to a login account. The account may change so we have to first create the directory then set the log output file to this directory. I tried to first log the logconfig.ini and then set the logging::add_file_log(...), but the file path set in the .ini files created too. If I don't setup the FileName in the .ini file, it throws a exception. Is there anyway to set the path and the file name separately? Or change the file path after loading the .ini config file? Thanks

1 0

Re: [Boost-users] Issue with Boost.Test using Oracle Developer Studio 12.5
by Leo Carreon 16 Apr '17

16 Apr '17

I have not received any response on this mail therefore I have decided to report a bug via tracs. The tracs ticket# 12877. From: Leo Carreon Sent: Tuesday, February 28, 2017 6:25 PM To: Boost Users Mailing List Subject: Issue with Boost.Test using Oracle Developer Studio 12.5 Hi, This is a continuation of the issues I’ve encountered with Boost 1.63.0 using Developer Studio 12.5. I’m assuming that even with the Boost 1.63.0 build issues that libraries unaffected by the build issues are usable. Therefore, I have attempted to build one of my small projects in both C++11 and C++14 modes. The builds of this small project failed with the following error message: "/opt/boost1.63.0/include/boost/test/unit_test_log.hpp", line 218: Error: boost::unit_test::unit_test_log_t::test_unit_skipped hides the virtual function boost::unit_test::test_observer::test_unit_skipped(const boost::unit_test::test_unit&). This error was encountered compiling a source file containing the following: #define BOOST_TEST_MODULE TestImport #include <boost/test/unit_test.hpp> Is this a Boost.Test issue or is it a Developer Studio 12.5 issue? If it is a Boost.Test issue, how do I resolve it? Kind regards, Leo

2 1

[build] Unexpected static libraries in 1.63
by Gavin Lambert 16 Apr '17

16 Apr '17

I've recently rebuilt Boost 1.63 locally for both Windows and Linux, requesting dynamic libraries only (link=dynamic). However several libraries are still being built in both static and dynamic forms: - chrono - system - timer - unit_test_framework Additionally some libraries are being built only in static forms: - exception - test_exec_monitor I assume the latter is intentional, as presumably some libraries can only work as static libraries. Is the former intentional or a bug? It seems like a bug. Or do these contain symbols that the dynamic libraries do not?

4 6

Re: [Boost-users] [Boost.Test] Using intel MKL instead of ACML with the boost testing framework
by anandram sundar 16 Apr '17

16 Apr '17

Update: This doesn’t seem to have anything to do with MKL. Just linking with all the boost libraries is enough to cause this. I was able to repro this with just a few files. I am fairly certain this is because of some issue with linking incorrect libraries. Please let me know. I realize that I don’t need all these libraries for the simple test cases I have written. My g++ version is 4.4.6 Boost version 1.63 File1: // cat mklmain.cpp #define BOOST_ALL_DYN_LINK #define BOOST_TEST_MAIN #include <boost/test/included/unit_test.hpp> File2: // cat mkl1.cpp #include <boost/test/unit_test.hpp> #include "logging-helper.h" BOOST_FIXTURE_TEST_SUITE(mkltest1, Fixture) BOOST_AUTO_TEST_CASE(math_test_functions1) { BOOST_LOG_SEV(lg, trace) << "Starting test case for mkl test 1"; float dot = 3; BOOST_TEST(dot == 3); BOOST_LOG_SEV(lg, trace) << "Ending test case for mkl test 1"; } BOOST_AUTO_TEST_SUITE_END() File3: // cat mkl2.cpp #include <boost/test/unit_test.hpp> #include "logging-helper.h" BOOST_FIXTURE_TEST_SUITE(mkltest2, Fixture) BOOST_AUTO_TEST_CASE(math_test_functions2) { BOOST_LOG_SEV(lg, trace) << "Starting test case for mkl test 2"; float dot = 3; BOOST_TEST(dot == 3); BOOST_LOG_SEV(lg, trace) << "Ending test case for mkl test 2"; } BOOST_AUTO_TEST_SUITE_END() File4: // cat logging-helper.h // I realize that not all these headers are necessary. Was trying out different things. #pragma once #define BOOST_LOG_DYN_LINK 1 #include <boost/move/utility_core.hpp> #include <boost/log/sources/logger.hpp> #include <boost/log/sources/record_ostream.hpp> #include <boost/log/sources/global_logger_storage.hpp> #include <boost/log/utility/setup/file.hpp> #include <boost/log/utility/setup/console.hpp> #include <boost/log/utility/setup/common_attributes.hpp> #include <boost/log/trivial.hpp> #include <boost/log/expressions.hpp> #include <boost/log/sinks/text_file_backend.hpp> #include <boost/log/sources/severity_logger.hpp> namespace logging = boost::log; namespace src = boost::log::sources; namespace sinks = boost::log::sinks; namespace keywords = boost::log::keywords; using namespace logging::trivial; class Fixture { public: src::severity_logger<severity_level> lg; Fixture(){ logging::core::get()->remove_all_sinks(); logging::add_console_log ( std::cout, keywords::format = "[%TimeStamp%]: %Message%" ); logging::add_common_attributes(); } }; My compile/link line is this g++ -I/home/anandrs/Downloads/boost_1_63_0 -L/home/anandrs/Downloads/boost_1_63_0/stage/lib mkl1.cpp mkl2.cpp mklmain.cpp -lboost_prg_exec_monitor -lboost_unit_test_framework -lboost_context -lboost_locale -lboost_log -lboost_log_setup -lboost_timer -lboost_type_erasure -lboost_wave -lboost_chrono -lboost_filesystem -lboost_graph -lboost_random -lboost_thread -lboost_wserialization -lboost_atomic -lboost_container -lboost_date_time -lboost_iostreams -lboost_math_c99 -lboost_math_c99f -lboost_math_c99l -lboost_math_tr1 -lboost_math_tr1f -lboost_math_tr1l -lboost_program_options -lboost_regex -lboost_serialization -lboost_signals -lboost_system -lboost_exception -lboost_test_exec_monitor -o BoostMKL valgrind ./BoostMKL ==83998== Memcheck, a memory error detector ==83998== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==83998== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==83998== Command: ./BoostMKL ==83998== Running 2 test cases... [2017-02-23 10:11:04.603945]: Starting test case for mkl test 2 [2017-02-23 10:11:04.759958]: Ending test case for mkl test 2 [2017-02-23 10:11:04.824863]: Starting test case for mkl test 1 [2017-02-23 10:11:04.830820]: Ending test case for mkl test 1 *** No errors detected ==83998== Invalid read of size 4 ==83998== at 0x93124B6: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /usr/lib64/libstdc++.so.6.0.13) ==83998== by 0x9A4AEBC: __cxa_finalize (in /lib64/libc-2.12.so) ==83998== by 0x5083745: ??? (in /local/home/anandrs/Downloads/boost_1_63_0/stage/lib/libboost_unit_test_framework.so.1.63.0) ==83998== by 0x50DBE00: ??? (in /local/home/anandrs/Downloads/boost_1_63_0/stage/lib/libboost_unit_test_framework.so.1.63.0) ==83998== by 0x9A4AB21: exit (in /lib64/libc-2.12.so) ==83998== by 0x9A33D63: (below main) (in /lib64/libc-2.12.so) ==83998== Address 0xa1d4cd0 is 16 bytes inside a block of size 32 free'd ==83998== at 0x4C26FD6: operator delete(void*) (vg_replace_malloc.c:480) ==83998== by 0x93124C8: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /usr/lib64/libstdc++.so.6.0.13) ==83998== by 0x9A4AB21: exit (in /lib64/libc-2.12.so) ==83998== by 0x9A33D63: (below main) (in /lib64/libc-2.12.so) ==83998== ==83998== Invalid free() / delete / delete[] / realloc() ==83998== at 0x4C26FD6: operator delete(void*) (vg_replace_malloc.c:480) ==83998== by 0x93124C8: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /usr/lib64/libstdc++.so.6.0.13) ==83998== by 0x9A4AEBC: __cxa_finalize (in /lib64/libc-2.12.so) ==83998== by 0x5083745: ??? (in /local/home/anandrs/Downloads/boost_1_63_0/stage/lib/libboost_unit_test_framework.so.1.63.0) ==83998== by 0x50DBE00: ??? (in /local/home/anandrs/Downloads/boost_1_63_0/stage/lib/libboost_unit_test_framework.so.1.63.0) ==83998== by 0x9A4AB21: exit (in /lib64/libc-2.12.so) ==83998== by 0x9A33D63: (below main) (in /lib64/libc-2.12.so) ==83998== Address 0xa1d4cc0 is 0 bytes inside a block of size 32 free'd ==83998== at 0x4C26FD6: operator delete(void*) (vg_replace_malloc.c:480) ==83998== by 0x93124C8: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /usr/lib64/libstdc++.so.6.0.13) ==83998== by 0x9A4AB21: exit (in /lib64/libc-2.12.so) ==83998== by 0x9A33D63: (below main) (in /lib64/libc-2.12.so) ==83998== ==83998== ==83998== HEAP SUMMARY: ==83998== in use at exit: 1,552 bytes in 34 blocks ==83998== total heap usage: 3,704 allocs, 3,698 frees, 221,397 bytes allocated ==83998== ==83998== LEAK SUMMARY: ==83998== definitely lost: 1,032 bytes in 28 blocks ==83998== indirectly lost: 0 bytes in 0 blocks ==83998== possibly lost: 0 bytes in 0 blocks ==83998== still reachable: 520 bytes in 6 blocks ==83998== suppressed: 0 bytes in 0 blocks ==83998== Rerun with --leak-check=full to see details of leaked memory ==83998== ==83998== For counts of detected and suppressed errors, rerun with: -v ==83998== ERROR SUMMARY: 112 errors from 2 contexts (suppressed: 6 from 6) Thanks, Anand On Tue, Feb 21, 2017 at 2:03 PM, anandram sundar <sundaranandram(a)gmail.com> wrote: > Hi, > I recently wrote some tests using the Boost testing framework and > everything was working fine until I used the intel MKL with my project. As > soon as I started linking these libraries, the tests started failing with a > segmentation fault. This happens after the test execution is done and when > the cleanup is happening. Looking at what valgrind outputs, it seems like > there is some memory being released which is invalid(not sure if it is > because of calling free on already freed memory). This actually happens > even if none of the code depends on the MKL. Just adding them to the linked > libraries is enough to cause this. > > GCC 4.9.3 > Boost ver 1.62 > > *==85160== Invalid read of size 4* > *==85160== at 0x10916C57: std::basic_string<char, > std::char_traits<char>, std::allocator<char> >::~basic_string() (in > /lib/libstdc++.so.6.0.20)* > *==85160== by 0x1104AEBC: __cxa_finalize (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x41981E2: ??? (in > /lib/libboost_unit_test_framework.so.1.62.0)* > *==85160== by 0x400EC5B: _dl_fini (in /lib64/ld-2.12.so > <http://ld-2.12.so>)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== Address 0x1262fab0 is 16 bytes inside a block of size 30 > free'd* > *==85160== at 0x4C26FD6: operator delete(void*) > (vg_replace_malloc.c:480)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > > > *==85160== Invalid free() / delete / delete[] / realloc()* > *==85160== at 0x4C26FD6: operator delete(void*) > (vg_replace_malloc.c:480)* > *==85160== by 0x1104AEBC: __cxa_finalize (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x41981E2: ??? (in > /lib/libboost_unit_test_framework.so.1.62.0)* > *==85160== by 0x400EC5B: _dl_fini (in /lib64/ld-2.12.so > <http://ld-2.12.so>)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== Address 0x1262faa0 is 0 bytes inside a block of size 30 free'd* > *==85160== at 0x4C26FD6: operator delete(void*) > (vg_replace_malloc.c:480)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > > > I am not sure why this is happening. Are there any known compatibility > issues between MKL and Boost testing framework. I was using ACML before > this and the tests were working fine with them. > > > Thanks, > Anand >

2 1

Howard Hinnant
by Leo Carreon 16 Apr '17

16 Apr '17

Hi Boost Users, Does any know how to contact Howard Hinnant by email? Kind regards, Leo

3 3

What is the effective way to use boost::asio::deadline_timer for udp socket receive_from?
by jupiter 14 Apr '17

14 Apr '17

Hi, My program needs a sync udp socket send / receiver so I use the deadline_timer as timeout for udp socket receive_from on Debian Jessie: boost::asio::deadline_timer deadline(io_service, boost::posix_time::seconds(2)); In checkDeadline function, when the timer expires, it calls socket.cancel, otherwise calls the deadline.async_wait(checkDeadline); again. Apparently when the program runs to socket.receive_from(), it is blocked and the timer is never called because both socket.receive_from and the timer in the same thread. I've been thinking to run the timer in another thread, but I checked Internet, there are comments said deadline_timer is not thread safe, please correct me if I am wrong here. It will be a simple solution for me if I can run timer on another thread. Anyone has other ideas to run the timer effectively? Appreciate your comments. Thank you.

4 8

Re: [Boost-users] udp::endpoint listen_endpoint invalid argument
by Bjorn Reese 12 Apr '17

12 Apr '17

On 04/11/2017 07:32 AM, jupiter via Boost-users wrote: > To simplify it, I changed to: > udp::endpoint listen_endpoint( > boost::asio::ip::address::from_string("localhost"), 15555); Quoting the documentation: "from_string Create an address from an IPv4 address string in dotted decimal form, or from an IPv6 address in hexadecimal notation." You need to resolve "localhost" first.

3 2

udp::endpoint listen_endpoint invalid argument
by jupiter 11 Apr '17

11 Apr '17

Hi, I built doc/html/boost_asio/example/timeouts/blocking_udp_client.cpp on Debian Jessie, but when I run it, I got Invalid argument on the statement of udp::endpoint listen_endpoint( boost::asio::ip::address::from_string(argv[1]), std::atoi(argv[2])); To simplify it, I changed to: udp::endpoint listen_endpoint( boost::asio::ip::address::from_string("localhost"), 15555); Appreciate any clues what's wrong with that statement and why it caused invalid argument? Thank you.

2 1

Thread Pool example
by Gonzalo Garramuño 10 Apr '17

10 Apr '17

Hi, I currently use boost (1.60) for my program and would like to have a part of it multithreaded (the creation of icons in a file requester). I would like to create those with a thread pool. I am currently using gcc 4.6.3, which is not yet c++11 compatible. I found no documentation on the usage of boost/thread/thread_pool.hpp so I turn to the list. Does anyone have an example of a thread pool with boost threads. Thanks in advance, -- Gonzalo Garramuño

3 3

Boost.Pool: singleton_pool - thread safe for any kind of threads?
by Igor Yakushin 07 Apr '17

07 Apr '17

Hi All, singleton_pool documentation claims that it is thread safe. It is not clear too me if this is applied to all kinds of threads or only the ones from Boost library. For example, I am using OpenMP which is external to Boost. Would singleton_pool still be thread safe or do I need to redefine Mutex? What if I later decide to use some other kind of threads like Intel Cilk Plus or TBB? Thank you, Igor

2 1

Boost Asio not built
by Balázs Bámer 07 Apr '17

07 Apr '17

Hi All, I have downloaded Boost 1.63 the second time. On my home computer, building it yielded all libraries. However, I do similar now at work, and it won't build Asio. First I do ./bootstrap.sh --with-libraries=all Then I build, but these are the results: balazs@bamer-debian:/opt/boost-1.63$ ls stage/lib/ |grep asio|wc 0 0 0 Although there are cpp files, that should be turned into a linbrary: balazs@bamer-debian:/opt/boost-1.63$ find |grep asio |grep cpp$|wc 214 214 9862 Asking bootstrap about what it would do shows it is not willing to build Asio: balazs@bamer-debian:/opt/boost-1.63$ ./b2 --show-libraries The following libraries require building: - atomic - chrono - container - context - coroutine - coroutine2 - date_time - exception - fiber - filesystem - graph - graph_parallel - iostreams - locale - log - math - metaparse - mpi - program_options - python - random - regex - serialization - signals - system - test - thread - timer - type_erasure - wave What should I do? Is there a dependency missing? Thank you in advance. Best regards: Balazs

5 6

How to design proper release of a boost::asio socket or wrapper thereof
by Christopher Pisz 06 Apr '17

06 Apr '17

I am making a few attempts at making my own simple asynch TCP server using boost::asio after not having touched it for several years. The latest example listing I can find is: http://www.boost.org/doc/libs/1_54_0/doc/html/boost_asio/tutorial/tutdaytim… The problem I have with this example listing is that it cheats and it cheats big, by making the tcp_connection a shared_ptr, such that it doesn't worry about the lifetime management of each connection. I am worried about the lifetime management of each connection. I figure the natural thing to do would be to keep some collection of tcp_connection objects or pointers to them inside tcp_server. Adding to that collection from the OnConnect callback and removing from that collection OnDisconnect. Note that OnDisconnect would most likely be called from an actual Disconnect method, which in turn would be called from OnReceive callback or OnSend callback, in the case of an error. Well, therein lies the problem. Consider we'd have a callstack that looked something like this: tcp_connection::~tcp_connection tcp_server::OnDisconnect tcp_connection::OnDisconnect tcp_connection::Disconnect tcp_connection::OnReceive This would cause errors as the call stack unwinds and we are executing code in a object that has had its destructor called...I think, right? I then thought to myself, well I could flag the tcp_connection as disconnected when it disconnects and then on some timer on the tcp_server, go through its collection and start deleting disconnected tcp_connection objects, but then the timer could fire after the flag is set, but before it returns from a OnReceive where an error occurred and I Disconnected as a response. I imagine everyone doing server programming comes across this scenario in some fashion. What is a strategy for handling it? I hope the explanation is good enough to follow. If not let me know and I will create my own source listing, but it will be very large. -- View this message in context: http://boost.2283326.n4.nabble.com/How-to-design-proper-release-of-a-boost-… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

Re: [Boost-users] How to design proper release of a boost::asio socket or wrapper thereof
by Bjorn Reese 06 Apr '17

06 Apr '17

On 04/05/2017 10:32 PM, Christopher Pisz via Boost-users wrote: > The problem I have with this example listing is that it cheats and it cheats > big, by making the tcp_connection a shared_ptr, such that it doesn't worry > about the lifetime management of each connection. That is not cheating. > Consider we'd have a callstack that looked something like this: > tcp_connection::~tcp_connection > tcp_server::OnDisconnect > tcp_connection::OnDisconnect > tcp_connection::Disconnect If Disconnect is an asynchronous operation, then it should not call OnDisconnect directly. You can post it on the io_service instead. > I imagine everyone doing server programming comes across this scenario in > some fashion. What is a strategy for handling it? Preferably shared_ptr, or io_service::post() if for some reason you cannot use shared_ptr, e.g. if the object has to be destroyed by a a specific thread.

3 3

[gsoc17] Help review Google Summer of Code proposals
by Niall Douglas 05 Apr '17

05 Apr '17

Dear Boost, Student proposals for Google Summer of Code are submitted, please help us decide which have the most merit. I have reduced the fifty something proposals submitted down to twenty seven which have some chance. To be able to view and rank the student proposals, please do the following: 1. Send to gsoc-admin(a)boost.org your Google login. We will invite you to view the student proposals on the Boost Google Drive. Until you receive the invitation email, you won't be able to view the proposals. 2. Go to https://goo.gl/forms/EVppdHsHMnjkcUoD3 which is a Google form where you can score the proposals. We have linked each proposal there to the Google Drive item and there you can rank a proposal between 1 and 5. Make sure you use the same email as your Google login in the form, otherwise we will ignore any forms submitted to prevent gaming the results. 3. Even if you can't rank all twenty seven proposals, try to do as many as you can and then PRESS SUBMIT at the end of the form (forgetting to press SUBMIT means we never get your rankings). The proposals are presented in random order per person so any work you do will be useful. 4. Please try to have your rankings done by Monday 10th. You may find reviewing the page at https://svn.boost.org/trac/boost/wiki/SoC2017 useful. 5. Finally, if you'd like to mentor any of the proposals, send to gsoc-admin(a)boost.org your Google login so we may invite you onto the Google website as a mentor. Many thanks in advance. Niall & Bryce

1 0

[Fusion] wide-char output
by Leo Cacciari 05 Apr '17

05 Apr '17

Hi, the documentation of the Boost.Fusion library (1.63.0) at http://www.boost.org/doc/libs/1_63_0/libs/fusion/doc/html/fusion/sequence/o… affirms that operator<< is defined in the boost::fusion namespace with the following synopsis: template <typename OStream, typename Sequence> OStream& operator<<(OStream& os, Sequence& seq); where the template parameter OStream is defined as "An output stream". Accordingly, I thought that the following would work: using boost::fusion::operator<<; fusion::vector<int, double, const char *> v = fusion::make_vector(42, 3.1415, "foobar"); std::wcout << "v = " << v << std::endl; However, the compiler (MSVC 9) complains that it has: "found no defined operator << taking a right-hand argument of type boost::fusion::vector<T0,T1,T2> with T0 = int, T1 = double, T2 = char *" If I replace std::wcout with its narrow-char sibling std::cout, everything works as expected; i.e. the code compiles and when run prints (42,3.1415, foobar). Looking into the source (file boost/fusion/sequence/io/out.hpp) it seems that the operator<< is only defined for left-hand argument of type std::ostream. Thus the questions: 1. Is this a bug and should I post a ticket about it? (I looked in the bugs database but I couldn't find it) 2. If it's a bug, are there any plan to patch it soon? 3. If not, does exist any reason why it shouldn't be patched nevertheless? If needed, I could volunteer for writing a patch. Thank for your attention -- Leo Cacciari Aliae nationes servitutem pati possunt. Populi Romani est propria libertas.

3 4

Query regarding Boost.Log
by Leo Carreon 02 Apr '17

02 Apr '17

Hi, Does Boost.Log require synchronization when multiple processes log to the same log file? Kind regards, Leo

1 0