- Boost-users - lists.boost.org

Re: [Boost-users] multiprecision modf
by Daniel Brake 03 Aug '16

03 Aug '16

Paul, Boost, Thanks for the quick reply! I haven’t looked into this in detail, but I think not, > but Boost.Math does > > #include <boost/math/special_functions/modf.hpp> > > You might also need to add this to your local function(s) to aid Argument > Dependant Lookup (ADL). > > BOOST_MATH_STD_USING Boost.Math and the BOOST_MATH_STD_USING solved the modf problem, so long as I include and using before including Karma. Since the compiler got past that, it generated a new error, related to log10, floor, and int comparison. I've had errors related to log10, floor, and ceil in the context of Eigen before. /u/ggael resolved them by explicit casting in certain places, see e.g. https://forum.kde.org/viewtopic.php?f=74&t=133404&p=359710#p359710 Here's the new error message: In file included from test/generating/mpfr_float.cpp:27: In file included from ./include/bertini2/io/generators.hpp:44: In file included from /usr/local/include/boost/spirit/include/karma.hpp:16: In file included from /usr/local/include/boost/spirit/home/karma.hpp:15: In file included from /usr/local/include/boost/spirit/home/karma/numeric.hpp:16: In file included from /usr/local/include/boost/spirit/home/karma/numeric/real.hpp:32: /usr/local/include/boost/spirit/home/karma/numeric/real_policies.hpp:263:39: error: incompatible operand types ('int' and 'typename enable_if_c<number_category<detail::expression<function, log10_funct<mpfr_float_backend<0, allocate_dynamic> >, number<mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, void, void> >::value == number_kind_floating_point, detail::expression<detail::function, detail::floor_funct<typename detail::backend_type<detail::expression<function, log10_funct<mpfr_float_backend<0, allocate_dynamic> >, number<mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, void, void> >::type>, detail::expression<function, log10_funct<mpfr_float_backend<0, allocate_dynamic> >, number<mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, void, void> > >::type' (aka 'boost::multiprecision::detail::expression<boost::multiprecision::detail::function, boost::multiprecision::detail::floor_funct<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic> >, boost::multiprecision::detail::expression<boost::multiprecision::detail::function, boost::multiprecision::detail::log10_funct<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic> >, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, void, void>, void, void>')) (traits::test_zero(n) ? 0 : floor(log10(n))) + 1; ^ ~ ~~~~~~~~~~~~~~~ /usr/local/include/boost/spirit/home/karma/numeric/detail/real_utils.hpp:170:24: note: in instantiation of function template specialization 'boost::spirit::karma::real_policies<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >::fraction_part<boost::spirit::karma::detail::output_iterator<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::unused_type> >' requested here r = r && p.fraction_part(sink, long_frac_part, prec, precision); ^ /usr/local/include/boost/spirit/home/karma/numeric/real_policies.hpp:94:30: note: in instantiation of function template specialization 'boost::spirit::karma::real_inserter<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<mpfr_float>, boost::spirit::unused_type, boost::spirit::unused_type>::call_n<boost::spirit::karma::detail::output_iterator<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::unused_type>, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return Inserter::call_n(sink, n, p); ^ /usr/local/include/boost/spirit/home/karma/numeric/detail/real_utils.hpp:56:31: note: in instantiation of function template specialization 'boost::spirit::karma::real_policies<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >::call<boost::spirit::karma::real_inserter<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<mpfr_float>, boost::spirit::unused_type, boost::spirit::unused_type>, boost::spirit::karma::detail::output_iterator<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::unused_type>, bertini::generators::BertiniNumPolicy<mpfr_float> >' requested here return p.template call<real_inserter>(sink, n, p); ^ /usr/local/include/boost/spirit/home/karma/numeric/real.hpp:192:35: note: in instantiation of function template specialization 'boost::spirit::karma::real_inserter<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<mpfr_float>, boost::spirit::unused_type, boost::spirit::unused_type>::call<boost::spirit::karma::detail::output_iterator<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::unused_type>, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return inserter_type::call(sink, traits::extract_from<T>(attr, context), p_) && ^ /usr/local/include/boost/spirit/home/karma/generate.hpp:69:45: note: in instantiation of function template specialization 'boost::spirit::karma::any_real_generator<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<mpfr_float>, boost::spirit::unused_type, boost::spirit::unused_type>::generate<boost::spirit::karma::detail::output_iterator<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::unused_type>, boost::spirit::context<boost::fusion::cons<const boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> &, boost::fusion::nil_>, boost::spirit::locals<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na> >, boost::spirit::unused_type, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return compile<karma::domain>(expr).generate(sink, context, unused, attr); ^ /usr/local/include/boost/spirit/home/karma/generate.hpp:91:23: note: in instantiation of function template specialization 'boost::spirit::karma::generate<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::karma::real_generator<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<mpfr_float> >, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return karma::generate(sink, expr, attr); ^ ./include/bertini2/io/generators.hpp:153:21: note: in instantiation of function template specialization 'boost::spirit::karma::generate<std::__1::back_insert_iterator<std::__1::basic_string<char> >, boost::spirit::karma::real_generator<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<mpfr_float> >, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return generate(sink, ^ test/generating/mpfr_float.cpp:53:47: note: in instantiation of function template specialization 'bertini::generators::Classic::generate<std::__1::back_insert_iterator<std::__1::basic_string<char> > >' requested here BOOST_CHECK(bertini::generators::Classic::generate(sink, z)); Any help with this one would be greatly appreciated. It feels beyond my diagnosis. It feels to me like I might should feed mpfr_float into Fusion to adapt it, so I can use the type directly with Karma. Here's the generator code so far: template <typename Num> struct BertiniNumPolicy : public karma::real_policies<Num> { // we want the numbers always to be in scientific format static int floatfield(Num n) { return std::ios_base::scientific; } static unsigned int precision(Num) { return std::numeric_limits<Num>::max_digits10; } }; template<> struct BertiniNumPolicy<mpfr_float> : public karma::real_policies<mpfr_float> { // we want the numbers always to be in scientific format static int floatfield(mpfr_float n) { return std::ios_base::scientific; } static unsigned int precision(mpfr_float const& x) { return x.precision(); } }; template<typename Num> using FullPrec = boost::spirit::karma::real_generator<Num, BertiniNumPolicy<Num> >; FullPrec<double> const full_prec_d = FullPrec<double>(); FullPrec<mpfr_float> const full_prec_mp = FullPrec<mpfr_float>(); template <typename OutputIterator> static bool generate(OutputIterator sink, mpfr_float const& c) { using boost::spirit::karma::generate; return generate(sink, // Begin grammar ( full_prec_mp ), // End grammar c // Data to output ); } As a last question, I am unsure about the use of the a function parameter in my specialization BertiniNumPolicy<mpfr_float>, particularly the precision(mpfr_float) function. In the documentation and examples I have seen for specializations, this function doesn't use the argument. Is it ok that it does, that it checks the actual precision of x??? See above code. An alternate method for me might be to just use the str() method provided by the number<...> from Multiprecision, but it seems like since this type is numeric, I'd like to be able to generate using the numeric generators from Karma. Thanks again! Daniel Brake > ---------- Forwarded message ---------- > From: "Paul A. Bristow" <pbristow(a)hetp.u-net.com> > To: <boost-users(a)lists.boost.org> > Cc: > Date: Wed, 3 Aug 2016 10:00:20 +0100 > Subject: Re: [Boost-users] multiprecision modf > > I haven’t looked into this in detail, but I think not, > > > > but Boost.Math does > > > > #include <boost/math/special_functions/modf.hpp> > > > > You might also need to add this to your local function(s) to aid Argument > Dependant Lookup (ADL). > > > > BOOST_MATH_STD_USING > > > > > http://www.boost.org/doc/libs/1_61_0/libs/math/doc/html/math_toolkit/config… > > > > *Table 11. Boost.Math Macros* > > > > “Provides using statements for many std:: (abs to sqrt) and boost::math > (rounds, modf) functions. This allows these functions to be called > unqualified so that ifargument-dependent Argument Dependent Lookup > <http://en.wikipedia.org/wiki/Argument-dependent_name_lookup> fails to > find a suitable overload, then the std:: versions will also be considered.” > > > > HTH > > > > Paul >

2 1

multiprecision modf
by Daniel Brake 03 Aug '16

03 Aug '16

Hi Boost, Does Boost.Multiprecision provide modf for floating point types? I need it for generating with Karma, unless the fact that mpfr_float with variable precision not having numeric_traits might get in the way. Thanks for any help. Error message follows. In file included from test/generating/mpfr_float.cpp:27: In file included from ./include/bertini2/io/generators.hpp:38: In file included from /usr/local/include/boost/spirit/include/karma.hpp:16: In file included from /usr/local/include/boost/spirit/home/karma.hpp:15: In file included from /usr/local/include/boost/spirit/home/karma/numeric.hpp:16: In file included from /usr/local/include/boost/spirit/home/karma/numeric/real.hpp:32: In file included from /usr/local/include/boost/spirit/home/karma/numeric/real_policies.hpp:21: /usr/local/include/boost/spirit/home/karma/numeric/detail/real_utils.hpp:115:33: error: no matching function for call to 'modf' U fractional_part = modf(n, &integer_part); ^~~~ /usr/local/include/boost/spirit/home/karma/numeric/real_policies.hpp:94:30: note: in instantiation of function template specialization 'boost::spirit::karma::real_inserter<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >, boost::spirit::unused_type, boost::spirit::unused_type>::call_n<boost::spirit::karma::detail::output_iterator<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::unused_type>, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return Inserter::call_n(sink, n, p); ^ /usr/local/include/boost/spirit/home/karma/numeric/detail/real_utils.hpp:56:31: note: in instantiation of function template specialization 'boost::spirit::karma::real_policies<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >::call<boost::spirit::karma::real_inserter<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >, boost::spirit::unused_type, boost::spirit::unused_type>, boost::spirit::karma::detail::output_iterator<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::unused_type>, bertini::generators::BertiniNumPolicy<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> > >' requested here return p.template call<real_inserter>(sink, n, p); ^ /usr/local/include/boost/spirit/home/karma/numeric/real.hpp:192:35: note: in instantiation of function template specialization 'boost::spirit::karma::real_inserter<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >, boost::spirit::unused_type, boost::spirit::unused_type>::call<boost::spirit::karma::detail::output_iterator<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::unused_type>, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return inserter_type::call(sink, traits::extract_from<T>(attr, context), p_) && ^ /usr/local/include/boost/spirit/home/karma/generate.hpp:69:45: note: in instantiation of function template specialization 'boost::spirit::karma::any_real_generator<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >, boost::spirit::unused_type, boost::spirit::unused_type>::generate<boost::spirit::karma::detail::output_iterator<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::unused_type>, boost::spirit::context<boost::fusion::cons<const boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> &, boost::fusion::nil_>, boost::spirit::locals<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na> >, boost::spirit::unused_type, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return compile<karma::domain>(expr).generate(sink, context, unused, attr); ^ /usr/local/include/boost/spirit/home/karma/generate.hpp:91:23: note: in instantiation of function template specialization 'boost::spirit::karma::generate<std::__1::back_insert_iterator<std::__1::basic_string<char> >, mpl_::int_<0>, boost::spirit::karma::real_generator<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> > >, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return karma::generate(sink, expr, attr); ^ ./include/bertini2/io/generators.hpp:149:21: note: in instantiation of function template specialization 'boost::spirit::karma::generate<std::__1::back_insert_iterator<std::__1::basic_string<char> >, boost::spirit::karma::real_generator<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>, bertini::generators::BertiniNumPolicy<boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> > >, boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on> >' requested here return generate(sink, ^ test/generating/mpfr_float.cpp:53:47: note: in instantiation of function template specialization 'bertini::generators::Classic::generate<std::__1::back_insert_iterator<std::__1::basic_string<char> > >' requested here BOOST_CHECK(bertini::generators::Classic::generate(sink, z)); ^ /usr/include/math.h:407:15: note: candidate function not viable: no known conversion from 'boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>' to 'double' for 1st argument extern double modf(double, double *); ^ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:940:46: note: candidate function not viable: no known conversion from 'boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>' to 'float' for 1st argument inline _LIBCPP_INLINE_VISIBILITY float modf(float __lcpp_x, float* __lcpp_y) _NOEXCEPT {return modff(__lcpp_x, __lcpp_y);} ^ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:941:46: note: candidate function not viable: no known conversion from 'boost::multiprecision::number<boost::multiprecision::backends::mpfr_float_backend<0, allocate_dynamic>, boost::multiprecision::expression_template_option::et_on>' to 'long double' for 1st argument inline _LIBCPP_INLINE_VISIBILITY long double modf(long double __lcpp_x, long double* __lcpp_y) _NOEXCEPT {return modfl(__lcpp_x, __lcpp_y);} Daniel Brake

3 2

boost::serialization::array for Orocos RTT
by Sambeet Panigrahi 02 Aug '16

02 Aug '16

Sir, I work on Orocos Real Time toolkit.Thhe project uses a boost::serialization::array however in the boost 1.44 I use there is no such header.Can you please tell me whether this header is really a part of Boost now? If no what can I use instead of that? I am posting the relevant build errors from RTT for a clearer idea: In file included from /home/sambeet/rtt-master/rtt/internal/DataSourceTypeInfo.hpp:44:0, from /home/sambeet/rtt-master/rtt/internal/DataSource.inl:5, from /home/sambeet/rtt-master/rtt/internal/DataSource.hpp:237, from /home/sambeet/rtt-master/rtt/OperationInterface.hpp:48, from /home/sambeet/rtt-master/rtt/OperationInterface.cpp:39: /home/sambeet/rtt-master/rtt/internal/../types/carray.hpp:99:48: error: expected ‘)’ before ‘<’ token carray( boost::serialization::array<T> const& orig) ^ /home/sambeet/rtt-master/rtt/internal/../types/carray.hpp:165:41: error: ‘array’ is not a member of ‘boost::serialization’ const carray<T>& operator=( boost::serialization::array<OtherT> const& orig ) { ^ /home/sambeet/rtt-master/rtt/internal/../types/carray.hpp:165:41: note: suggested alternative: In file included from /usr/include/boost/serialization/array.hpp:151:0, from /home/sambeet/rtt-master/rtt/internal/../types/carray.hpp:42, from /home/sambeet/rtt-master/rtt/internal/DataSourceTypeInfo.hpp:44, from /home/sambeet/rtt-master/rtt/internal/DataSource.inl:5, from /home/sambeet/rtt-master/rtt/internal/DataSource.hpp:237, from /home/sambeet/rtt-master/rtt/OperationInterface.hpp:48, from /home/sambeet/rtt-master/rtt/OperationInterface.cpp:39: /usr/include/boost/array.hpp:60:11: note: ‘boost::array’ class array { ^ In file included from /home/sambeet/rtt-master/rtt/internal/DataSourceTypeInfo.hpp:44:0, from /home/sambeet/rtt-master/rtt/internal/DataSource.inl:5, from /home/sambeet/rtt-master/rtt/internal/DataSource.hpp:237, from /home/sambeet/rtt-master/rtt/OperationInterface.hpp:48, from /home/sambeet/rtt-master/rtt/OperationInterface.cpp:39: /home/sambeet/rtt-master/rtt/internal/../types/carray.hpp:165:75: error: expected primary-expression before ‘>’ token const carray<T>& operator=( boost::serialization::array<OtherT> const& orig ) { ^ /home/sambeet/rtt-master/rtt/internal/../types/carray.hpp:165:77: error: expected primary-expression before ‘const’ const carray<T>& operator=( boost::serialization::array<OtherT> const& orig ) { ^ /home/sambeet/rtt-master/rtt/internal/../types/carray.hpp:165:89: error: declaration of ‘operator=’ as non-function const carray<T>& operator=( boost::serialization::array<OtherT> const& orig ) { ^ make[2]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/OperationInterface.cpp.o] Error 1 make[1]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/all] Error 2 make: *** [all] Error 2 Regards Sambeet

2 1

Windows installation issues
by Alexander Carôt 01 Aug '16

01 Aug '16

Hi all, after having switched from OSX and Linux to Windows 10 I have issues compiling boost (1.61)with the MinGW compiler. The very first step fails: bootstrap.bat mingw results in not finding a right path, denying access and aborting the installation. So far I only found this article: https://andres.jaimes.net/698/use-c-with-mingw-and-netbeans-in-windows/ but it does not contain further info how (and where) to add additional info (I added c:\MinGW\bin to my PATH but it didn’t help). Any help appreciated, thanks in advance Alex --

6 8

Python TypeError with application compiled with CXX11_ABI=0
by Jackson Wiegman 29 Jul '16

29 Jul '16

Hi, I have an application I am trying to compile on Ubuntu 16.04. This is using GCC 5.4.0 and libboost 1.58.0 (stock libraries). The application has a linking to a library that was built with GCC 4.*, so I have to compile with D_GLIBCXX_USE_CXX11_ABI=0 to get backwards comparability (otherwise I have undefined abi:cxx11 links). However when I do this, I get a TypeError in Python: TypeError: No registered converter was able to produce a C++ rvalue of type > std::string from this Python object of type str It looks like boost is having a problem working without the ABI. Does anyone have a work-around or a patch for this? Jackson

2 2

[Python] gcc error compiling boost
by Àlex Jarauta 29 Jul '16

29 Jul '16

Dear all, my name is Alex and I am a postdoc at the University of Alberta, Edmonton, Canada. I am working with an in-house opensource code that uses boost to wrap C++ code with Python. In the latest version of our code, one has to download boost manually and compile it. I have tried wot two different versions (1.59 and 1.60) and I can compile them with python 2.7. However, if I try to compile it using either Python 3.3 or 3.5, I always get the same error: "./boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory # include <pyconfig.h>" I have been looking for this error for a while, but I have not been able to find a proper solution. I wonder if you could help me on this matter. Thank you very much for your attention. Best regards, Àlex

2 1

Graph: Trying to filter on custom properties
by Amit Prakash Ambasta 29 Jul '16

29 Jul '16

How should I be writing the get_filtered_graph in a generic way? #include <map> #include <string> #include <vector> #include <iostream> #include <boost/graph/adjacency_list.hpp> #include <boost/property_map/property_map.hpp> #include <boost/graph/filtered_graph.hpp> #include <boost/graph/graph_utility.hpp> template <typename F> struct EdgeProperty { F features; EdgeProperty() = default; EdgeProperty(const F& f) : features(f) {} }; template <typename EM, typename F> struct filtered_edge { F filters; EM emap; filtered_edge() = default; filtered_edge(EM emap_, F filters_) : emap(emap_), filters(filters_) {} template <typename E> bool operator()(const E& e) { auto e_prop = get(emap, e); auto e_feat = e_prop.features; for (auto it: e_feat) { if (get(e_feat, it.first) != it.second) { return false; } } return true; } }; template<typename G, typename F> G get_filtered_graph(G& g, F& filters) { typedef filtered_edge<boost::property_map<G, EdgeProperty<F> >, F> filter_fn; filter_fn filter{get(&EdgeProperty<F>::features, g), filters}; boost::filtered_graph<G, filter_fn> fg(g, filter); return fg; } typedef std::map<std::string, int> dict; typedef boost::adjacency_list< boost::vecS, boost::vecS, boost::directedS, boost::no_property, EdgeProperty<dict> > Graph; Graph create_empty_graph() noexcept { return {}; } int main() { const char* name = "ABCDE"; auto g = create_empty_graph(); auto v0 = boost::add_vertex(g); auto v1 = boost::add_vertex(g); auto v2 = boost::add_vertex(g); dict d01; d01["a"] = 1; dict d12; d12["b"] = 1; dict fil; fil["a"] = 1; auto ep01 = EdgeProperty<dict>{ dict{} }; boost::add_edge(v0, v1, d01, g); boost::add_edge(v1, v2, d12, g); std::cout << "Before filter" << std::endl; boost::print_graph(g, name); auto fg = get_filtered_graph(g, fil); std::cout << "After filter" << std::endl; boost::print_graph(fg, name); Graph ga; }

2 2

[boost.geometry] concept namespace conflicts with new concept keyword (gcc 6.1)
by kique G 28 Jul '16

28 Jul '16

Hello, I am using boost.geometry with gcc 6.1 and I am finding conflicts between the new concept keyword (-fconcepts) and the concept namespace: /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:33:50: error: expected identifier before 'concept' Am I missing something? If not, are there any plans for renaming this namespace? Do you know of any other incompatibilities between the boost libraries and the concepts TS? Thanks and best regards, Enrique Garcia

2 2

SVGMath no longer available
by Je suis la poubelle 27 Jul '16

27 Jul '16

Hi, I don't have any question to ask (yet :) ) but have a comment. In the folder "libs\math\doc\html\math_toolkit", there's the file sf_implementation.html. Inside this file, there's a section called "Creating and Managing the Equations". Inside it, you talked about a program called SVGMath (with a hyperlink). However, the hyperlink points to a website which no longer exists. Have a nice day

2 1

[boost.geometry] Why point coordinates are stored to SVG as integers?
by Mikhail Matrosov 27 Jul '16

27 Jul '16

Hello, I'm using boost::geometry::svg_mapper to save my shapes with floating point coordinates into an .svg file. It works great, but they are stored as integers. I can see this line in svg_mapper.hpp: namespace detail { namespace svg { typedef model::point<int, 2, cs::cartesian> svg_point_type; }} Thus svg_point is clearly defined to have integer coordinates. However, it is not convenient - SVG handles floating point coordinated perfectly well. Why not using original type of the serialized collection and let streams handle representation? ----- Best regards, Mikhail Matrosov

2 1