August 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

boost fileystem issue
by Olivier Tristan 20 Oct '17

20 Oct '17

Hi Guys, I would like to bump this particular issue that is quite annoying for me. Basically it crashes as soon as you call boost::filesystem::exists in the ctor of a static variable initialized at program startup https://svn.boost.org/trac10/ticket/12987 Looks like there was a fix 4 month ago but this hasn't been pushed into the trunk yet Any idea how to push the process forward ? Thanks ! -- Olivier Tristan Research & Development www.uvi.net

2 2

Help on boost::iostreams::gzip_compressor: Linker error
by Uthpal Urubail 31 Aug '17

31 Aug '17

Experts, I am getting below linker error on gzip compressor usage. Any help is highly appreciated. I have already tried linking boost_iostreams.lib & zlib.lib Code Description LNK2001 unresolved external symbol "int const boost::iostreams::zlib::default_compression" (?default_compression@zlib@iostreams@boost@@3HB) & Code Description LNK2019 unresolved external symbol "protected: __cdecl boost::iostreams::detail::zlib_base::~zlib_base(void)" (??1zlib_base@detail@iostreams@boost@@IEAA@XZ) referenced in function "int `public: __cdecl boost::iostreams::detail::zlib_compressor_impl<class std::allocator<char> >::zlib_compressor_impl<class std::allocator<char> >(struct iostreams::detail::zlib_params const &)'::`1'::dtor$0" (?dtor$0@?0???0?$zlib_compressor_impl@V?$allocator@D@std@@@detail@iostreams@boost@@QEAA@AEBUzlib_params@23@@Z@4HA) Regards, UJ

1 0

UDP Echo Server
by Mark Hieber 25 Aug '17

25 Aug '17

Hi,

3 3

[fiber][asio] Problem running http://www.boost.org/doc/libs/1_65_0/libs/fiber/examples/asio/autoecho.cpp
by Mark Hieber 24 Aug '17

24 Aug '17

Hi, I am using cmake 3.9.1 and Boost 1.65.0. I have downloaded the autoecho.cpp file and the corresponding yield.hpp, detail/yield.hpp and round_robin.hpp from http://www.boost.org/doc/libs/1_65_0/libs/fiber/examples/asio. When I run my program (just these 4 files, with no modifications), I get this output: Thread A: started Thread A: A0: echo-server started Segmentation fault Using print statements the seg-fault happens in the io_svc->run(); call. If anyone can help me with this, I would appreciate it. BTW, I am running on Ubuntu 16.04.3 LTS Thanks, Mark

2 1

Portable file I/O with system error codes support
by Oleg Andriyanov 23 Aug '17

23 Aug '17

Hi, I'm looking for a portable way to open a file, read some data from it, and do a proper error reporting in case of error. Apparently std::fstream is not suitable for this task because it does not provide means to retrieve original error code or even some human readable description of what went wrong (checking errno does not count since the standard does not guarantee it is set by any functions in std::fstream). I'm wondering if boost::iostreams can do that, but I've found nothing this far that could help in getting the error code. I've also tried boost::filesystem::fstream, but no luck. Users of large frameworks like Qt have advantage of their portable wrappers for file I/O like QFile. Are there any means in Boost which provide similar functionality? Related StackOverflow question: https://stackoverflow.com/questions/45840686/portable-way-to-read-a-file-in… Thanks.

3 2

[release] Boost 1.65.0
by Daniel James 21 Aug '17

21 Aug '17

Release 1.65.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 two new libraries and numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/history/version_1_65_0.html> You can also download directly from: <https://dl.bintray.com/boostorg/release/1.65.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

1 0

Is there a C++ implementation for numerical quadrature/cubature?
by Easior Lars 20 Aug '17

20 Aug '17

Hi, all in the list! I need some functions to handle numerical quadrature/cubature in C++. I found that only few packages, e.g. GSL, could do this end. However, those ones are not pure C++ implementations. Although, odeint package in Boost can partially satisfy my need. I want to know whether there is a C++ implementation for numerical quadrature/cubature in Boost. Any suggestion? -- Best wishes, Easior ------ "It was the age of wisdom, it was the age of foolishness, it was the epoch of belief, it was the epoch of incredulity, it was the season of Light, it was the season of Darkness, it was the spring of hope, it was the winter of despair, we had everything before us, we had nothing before us, we were all going direct to heaven, we were all going direct the other way - in short, the period was so far like the present period, that some of its noisiest authorities insisted on its being received, for good or for evil, in the superlative degree of comparison only." TALES OF TWO CITIES, by Charles Dickens

3 5

[Boost][Container] Why is flat_set default constructor explicit?
by dariomt＠gmail.com 17 Aug '17

17 Aug '17

Hi all, I just found out that all Boost.Container default constructors are implicit (just as I would expect) except for flat_set. Quoting from [1]: explicit flat_set() noexcept(/*snip*/); Effects: Default constructs an empty container. Why is flat_set different than the other containers? Is this an oversight? FWIW this issue is breaking my C++14 code (for both clang and gcc) when switching from std::set to boost::container::flat_set, minimal repro follows: #include <boost/container/flat_set.hpp> #include <set> #ifndef USE_STD_SET using S = boost::container::flat_set<int>; #else using S = std::set<int>; #endif struct A { int i; S s; }; int main() { A a1; // OK A a2 {0, {{}} }; // OK A b1 {}; // FAILS A b2 {0}; // FAILS A b3 {0, {}}; // FAILS } A f() { return {}; // FAILS } Using Bost 1.64.0 in case that matters. Any help appreciated. [1] http://www.boost.org/doc/libs/1_64_0/doc/html/boost/container/flat_set.html…

2 1

Re: [Boost-users] Boost 1.65.0 Release Candidate 4
by Marshall Clow 17 Aug '17

17 Aug '17

On Wed, Aug 16, 2017 at 8:33 PM, Marshall Clow <mclow.lists(a)gmail.com> wrote: > The fourth (and hopefully final) release candidates for the 1.65.0 release > are now available at: > > https://dl.bintray.com/boostorg/release/1.65.0/source/ > [snippage] 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. * Builds successfully with Apple Clang [Apple LLVM version 8.0.0 (clang-800.0.42.1)] with C++03/11/14/1z * Builds successfully with Clang Trunk [clang version 6.0.0 (trunk 310587)] with C++03/11/14 * Built successfully with Clang Trunk [clang version 6.0.0 (trunk 310587)] with C++1z except for Boost.Locale. -- Marshall

2 1

Boost 1.65.0 Release Candidate 4
by Marshall Clow 17 Aug '17

17 Aug '17

The fourth (and hopefully final) release candidates for the 1.65.0 release are now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ [ Note: The RC1s/RC2s/RC3s are in that directory, too - make sure you get the right files! ] Changes since RC3: * Fix a bug in Boost.Thread where timed waits were waiting for a very long time. Changes since RC2: * Fix a crashing bug in Boost.ASIO * Fix a compilation error when including both <boost/math_fwd.hpp> and <boost/math/common_factor_ct.hpp> * An update to Boost.Spirit to fix compilation errors on Mac OS with -std=c++17 Changes since RC1: * An update to Boost.Config so that the flags BOOST_NO_CXX98_RANDOM_SHUFFLE and BOOST_NO_CXX98_BINDERS are now set appropriately for libc++. (This fixes the compilation errors for Boost.Test) * An update to Boost.Fiber to fix compilation errors * An update to Boost.Wave to fix compilation errors on Mac OS with -std=c++17 The SHA256 checksums are as follows: 5d255d1ff8460d52dffcf9a9b55d908ae704027a66c590ec774096effaea26c1 boost_1_65_0_rc4.7z 911602d830ea5d16483d1e565b9859d120d03f2e5176017226ef391eb9d17fc8 boost_1_65_0_rc4.tar.bz2 369e06dc787d32b0fbaae020f33d814c9e7b77263acb859776968e623035f760 boost_1_65_0_rc4.tar.gz a9c6b8346b05ea43ac4278e80036a9e956ea99fc61f0b7f55469471af2df934c boost_1_65_0_rc4.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. Thanks! -- The release managers

2 1

Where we are 1.65.0
by Marshall Clow 16 Aug '17

16 Aug '17

RC1 came out on Monday, and it had some problems. Specifically: * Some libraries didn't build with ToT clang/libc++ (Locale, Wave and Test) This is because in C++17, some deprecated library features have been removed. [bind1st, mem_fun, auto_ptr, random_shuffle, etc ] Boost.Config has support for these removals, but this was ... incomplete. [ This is on me; I did the partial job of adding these to Config's libc++ support a while back ] Normally, I would be tempted to say "Well, clang 5 is not shipping yet, and so we can put this off until 1.66.0". But both clang 5 and C++17 are imminent (they will both happen well before the 1.66 release, and so I think we should fix this now. Also, a future version of MSVC will have the same library issues. So I have committed a fix for Boost.Config that fixes the Boost.Test issues. Hartmut has fixed most of the Boost.Wave issues. Artymom has a fix for Boost.Locale. Windows/MSVC builds look good across the board. * Boost.Fiber fails to build on Mac OS with anything other than -std=c++03. There is a fix in develop for this; but there's still a bunch of tests failing. * There's a problem from the beta in Boost.Math. The regression regarding boost/math/common_factor_ct.hpp (vs > math_fwd.hpp) seems to be still there. (For details please see the > original mail and replies: > https://lists.boost.org/Archives/boost/2017/07/237452.php) > What I presume is the fix (https://github.com/boostorg/math/pull/75) was > merged into develop about 12 hours ago, some automatic CI tests still > running. * There's a problem with ScopeExit and Visual C++ 2017 With Visual C++ 2017 and /permissive-, ScopeExit is still broken, for which > there's an open PR: > https://github.com/boostorg/scope_exit/pull/3 > Looks good otherwise on MSVC 14.11, tested with /std=cpplatest and > _HAS_AUTO_PTR_ETC=1, targeting Windows 10 and XP, 32 bit and 64 bit, built > as static libraries. >

5 5

constructing rationals from mpfr_floats [multiprecision]
by Dani Brake 15 Aug '17

15 Aug '17

Hi, 1) I am getting signaling due to division by 0. The following lines are faulty: mpfr_float p("1.1"); mpq_rational q(p); signal: integer divide by zero; whereas this succeeds: mpq_rational q(1.1); any one seen this before? i'm on compiler Apple LLVM version 8.0.0 (clang-800.0.38) ,with homebrew-provided boost 1.64, mpfr 3.1.5, gmp 6.1.2. -- 2) I also expected to be able to construct rationals as mpq_rational q("1.1") but it fails to parse using the built-in constructor. i mean, i understand why (1.1 isn't a rational), but given that i can construct a rational from a double, i figured that i'd get something reasonable from "1.1", namely 11/10. -- thanks! dani brake university of wisconsin eau claire ps i am not disabling mixed double-multiprecision arithmetic in this scenario, in case you have been reading my other questions this last week

1 0

Re: [Boost-users] deleting operators to forbid mixed arithmetic? [multiprecision]
by Dani Brake 15 Aug '17

15 Aug '17

Paul and John, Putting a macro bracket around this might make it generally useful, perhaps > something like: > > #ifdef BOOST_MULTIPRECISION_NO_DOUBLE_OPS (BUILTIN_OPS would include > float and long double?) > > … > > template <class Backend> > struct is_compatible_arithmetic_type<double, number<Backend> > : public > mpl::false_ {}; > > say > #endif > > If you find this useful, you could create a GIT Pull Request, or just > email the file changed. You won’t be the only one J. Defining the macro > BOOST_MULTIPRECISION_NO_DOUBLE_OPS could be a way to detect dodgy > conversions that need to be changed to keep full precision. I implemented this in my codebase, and had few ill effects. Some unexpected conversions, but I did find this disabling very useful. Wrapping it in a macro bracket and making it officially supported would be fabulous. I think it should go in number_base.hpp at line 110 or so. If we wanted to make it robust and thorough, I think we need to consider turning off implicit constructors from disabled types, too. I believe that what we have so far only disables arithmetic. Dani

1 0

Re: [Boost-users] Problem building Boost 1.64.0 with Oracle Developer Studio 12.6
by Leo Carreon 15 Aug '17

15 Aug '17

It’s now nearly a week since I sent this email and I have not received a comment from anyone from Boost. Does this mean we have no experience building on Developer Studio 12.6 or Boost doesn’t care whether it works on Solaris or not. I suspect Problem #2 may be a Solaris issue but I’m not sure about Problem #1 because even the guys from Oracle have no comment about it. I would appreciate a comment from the maintainer of Boost.Optional. From: Leo Carreon Sent: Wednesday, August 9, 2017 10:52 AM To: Boost Users Mailing List Subject: Problem building Boost 1.64.0 with Oracle Developer Studio 12.6 Hi Boosters, I have been trying to build Boost 1.64.0 with Oracle Developer Studio 12.6 on Oracle Solaris 11.3 x86_64. There are two errors encountered during the build. They are: 1. Problem with Boost.Optional with this error messages: "libs/log/src/named_scope.cpp", line 118: Error: Use of overloaded binary operator '=' is ambiguous. "./boost/optional/optional.hpp", line 900: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. "./boost/optional/optional.hpp", line 962: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. 2. Problem with Boost.Python with this error message: "libs/python/src/numpy/dtype.cpp", line 61: Error: NPY_FLOAT16 is not defined. Note that these two errors are the cause of 9 Boost shared libraries to not be generated. I would appreciate it very much if someone could give me some pointers on how to resolve the above issues. Kind regards, Leo

3 2

[Log][Optional][Python] Problem building Boost 1.64.0 with Oracle Developer Studio 12.6
by Leo Carreon 15 Aug '17

15 Aug '17

Hi, This is a resend with the suggested change on the subject line. I have been trying to build Boost 1.64.0 with Oracle Developer Studio 12.6 on Oracle Solaris 11.3 x86_64 in C++14 mode. There are three errors encountered during the build. They are: 1. Problem with Boost.Log with this error message: >> Assertion: (../lnk/initializer.cc, line 1865) while processing ./boost/log/expressions/message.hpp at line 98. My comment: Acknowledged by Oracle as a compiler issue. 2. Problem with Boost.Optional with this error messages: "libs/log/src/named_scope.cpp", line 118: Error: Use of overloaded binary operator '=' is ambiguous. "./boost/optional/optional.hpp", line 900: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. "./boost/optional/optional.hpp", line 962: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. My comment: Ambiguous boost::optional<>::operator=(), possibly a Boost configuration issue or compiler SFINAE issue. I’m not that fluent with SFINAE to be able to figure this out. 3. Problem with Boost.Python with this error message: "libs/python/src/numpy/dtype.cpp", line 61: Error: NPY_FLOAT16 is not defined. My comment: Possibly a Solaris package installation issue due to no support contract. (numpy package fails to install) I would appreciate it very much if someone could give me some pointers on how to resolve the above issues. Kind regards, Leo

1 0

Boost 1.65.0 Release Candidate 3
by Marshall Clow 14 Aug '17

14 Aug '17

The third (and hopefully final) release candidates for the 1.65.0 release are now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ [ Note: The RC1s and RC2s are in that directory, too - make sure you get the right files! ] Changes since RC2: * Fix a crashing bug in Boost.ASIO * Fix a compilation error when including both <boost/math_fwd.hpp> <boost/math/common_factor_ct.hpp> * An update to Boost.Spirit to fix compilation errors on Mac OS with -std=c++17 Changes since RC1: * An update to Boost.Config so that the flags BOOST_NO_CXX98_RANDOM_SHUFFLE and BOOST_NO_CXX98_BINDERS are now set appropriately for libc++. (This fixes the compilation errors for Boost.Test) * An update to Boost.Fiber to fix compilation errors * An update to Boost.Wave to fix compilation errors on Mac OS with -std=c++17 The SHA256 checksums are as follows: 1d844a958656e76b140292ec1cbfe770d9916166c16e13b59d3dac1df3b7ef40 boost_1_65_0_rc3.7z 3fc2877cf5da4bbb0c91eab058d2e6764155e705e9c3e2dce2a0248936079675 boost_1_65_0_rc3.tar.bz2 e065b53d7f5326cc20d246b518facedb4407391aaf9fd4a1c90001e0c85accab boost_1_65_0_rc3.tar.gz 96b2ba69c6045060d1dfe012218457870200c2c22af60eb855bab5ffb75c13a2 boost_1_65_0_rc3.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. Thanks! -- The release managers

1 1

Re: [Boost-users] deleting operators to forbid mixed arithmetic? [multiprecision]
by Dani Brake 14 Aug '17

14 Aug '17

> > So in principle you just define a full or partial specialization, for > example: > template <class Backend> > struct is_compatible_arithmetic_type<double, number<Backend> > : public > mpl::false_ {}; > and then cross your fingers and hope for the best ;) Thanks for the suggestion, i'll give it a try. \e crosses fingers ~dani

2 1

Re: [Boost-users] deleting operators to forbid mixed arithmetic? [multiprecision]
by Dani Brake 13 Aug '17

13 Aug '17

> > Been there, done that – fallen into the big pit awaiting the unwary mixing > double and multiprecision – again and again… L > I am being bit by this one hard. Converted a bunch of multipliers and tolerances from mpfr_floats to doubles in an effort to simplify some code, and now mixed precision is introducing error. > I think that you don’t really want to delete a family of operator*s – what > you DO want to get a warning when there is loss of significance, similar to > the warning when you fit a double into a float. > > It’s OK to multiply (or other ops) with a double as long as this doesn’t > lose any bits or digits of precision. > > So multiplying by 0.5 is OK, but not by multiplying 0.1 (the > multiprecision type needs FP_type(1)/10 to represent 0.1 as accurately as > possible for the FP type). > Multiplying by 0.1 is a common desire in my household (adaptive precision solving of polynomials). If only the compiler provided a trait bool is_exactly_representable(double) > so that a warning could be issued… > This is a bit tricky, because any double is by definition exactly representable by a double, right?. You would want is_exactly_representable to get the value before being transformed into a double? Another issue I foresee having to deal with is runtime parsing. Forbid the runtime user from feeding doubles problematic numbers. Thanks for the help, Dani

1 0

Re: [Boost-users] Problem building Boost 1.64.0 with Oracle Developer Studio 12.6
by Leo Carreon 12 Aug '17

12 Aug '17

It appears that Problem #1 is possibly a Boost configuration issue but may also be an issue with the compiler to do with enable_if. Two Boost.Optional member functions using enable_if are showing up in the lookup. Can anyone else comment? Problem #2 is possibly a Python package issue which can only be resolved by having a Solaris support contract because I’m unable to install the required packages to resolve the problem. From: Leo Carreon Sent: Wednesday, August 9, 2017 10:52 AM To: Boost Users Mailing List Subject: Problem building Boost 1.64.0 with Oracle Developer Studio 12.6 Hi Boosters, I have been trying to build Boost 1.64.0 with Oracle Developer Studio 12.6 on Oracle Solaris 11.3 x86_64. There are two errors encountered during the build. They are: 1. Problem with Boost.Optional with this error messages: "libs/log/src/named_scope.cpp", line 118: Error: Use of overloaded binary operator '=' is ambiguous. "./boost/optional/optional.hpp", line 900: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. "./boost/optional/optional.hpp", line 962: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. 2. Problem with Boost.Python with this error message: "libs/python/src/numpy/dtype.cpp", line 61: Error: NPY_FLOAT16 is not defined. Note that these two errors are the cause of 9 Boost shared libraries to not be generated. I would appreciate it very much if someone could give me some pointers on how to resolve the above issues. Kind regards, Leo

1 0

Re: [Boost-users] Problem building Boost 1.64.0 with Oracle Developer Studio 12.6
by Leo Carreon 12 Aug '17

12 Aug '17

BTW, I forgot to mention a third issue which has been acknowledged by Oracle as a problem with the compiler: 3. Problem with Boost.Log with this error message: >> Assertion: (../lnk/initializer.cc, line 1865) while processing ./boost/log/expressions/message.hpp at line 98. From: Leo Carreon Sent: Wednesday, August 9, 2017 10:52 AM To: Boost Users Mailing List Subject: Problem building Boost 1.64.0 with Oracle Developer Studio 12.6 Hi Boosters, I have been trying to build Boost 1.64.0 with Oracle Developer Studio 12.6 on Oracle Solaris 11.3 x86_64. There are two errors encountered during the build. They are: 1. Problem with Boost.Optional with this error messages: "libs/log/src/named_scope.cpp", line 118: Error: Use of overloaded binary operator '=' is ambiguous. "./boost/optional/optional.hpp", line 900: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. "./boost/optional/optional.hpp", line 962: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'. 2. Problem with Boost.Python with this error message: "libs/python/src/numpy/dtype.cpp", line 61: Error: NPY_FLOAT16 is not defined. Note that these two errors are the cause of 9 Boost shared libraries to not be generated. I would appreciate it very much if someone could give me some pointers on how to resolve the above issues. Kind regards, Leo

1 0

deleting operators to forbid mixed arithmetic? [multiprecision]
by Dani Brake 12 Aug '17

12 Aug '17

Hi, I'd like to forbid multiplication of Boost.Multiprecision floating point numbers by doubles. Any tips? I think I want to delete a family of operator*s, but am having a hard time coming up with which ones. Thanks, Dani Brake University of Wisconsin Eau Claire

3 2

Boost 1.65.0 Release Candidate 2
by Marshall Clow 12 Aug '17

12 Aug '17

The second release candidates for the 1.65.0 release are now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ [ Note: The RC1's are in that directory, too - make sure you get the right files! ] Changes from RC1: * An update to Boost.Config so that the flags BOOST_NO_CXX98_RANDOM_SHUFFLE and BOOST_NO_CXX98_BINDERS are now set appropriately for libc++. (This fixes the compilation errors for Boost.Test) * An update to Boost.Fiber to fix compilation errors * An update to Boost.Wave to fix compilation errors on Mac OS with -std=c++17 The SHA256 checksums are as follows: 786ccb478a82ef526fb8649841d2e863af90d7ea31217bb2e938d87aff06cf23 boost_1_65_0_rc2.7z 83dbc7179271825c55a59c26f30cf9de53bb8b42006d920948bad709f5372af9 boost_1_65_0_rc2.tar.bz2 493cbf33a8837b44f87e3ac8a37ec32b9a0a27b8cdb03eac6237a16027a03809 boost_1_65_0_rc2.tar.gz 40e4ccbd52322f9a8cb6e1829075c810d8aad8851f3efb2b3da7fcff6963e14d boost_1_65_0_rc2.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. Thanks! -- The release managers

2 4

[serialization] archive testing
by Sergey Spiridonov 09 Aug '17

09 Aug '17

Hi, 1. The following works with xml_archive: cd boost_1_64_0/libs/serialization/test bjam -sBOOST_ARCHIVE_LIST=xml_archive.hpp 2. Example from documentation[1] does not work for me. Documentation tells[1]: -------------------------- To test a new archive, for example, portable binary archives, with the gcc compiler, make a header file portable_binary_archive.hpp and invoke bjam with -sBOOST_ARCHIVE_LIST=portable_binary_archive.hpp This process in encapsulated in the shell or cmd script library_test whose command line is library_test --toolset=gcc -sBOOST_ARCHIVE_LIST=portable_binary_archive.hpp ------------------------- [1] http://www.boost.org/doc/libs/1_64_0/libs/serialization/doc/archive_referen… I created boost_1_64_0/libs/serialization/test/portable_binary_archive.hpp with following lines: #include <libs/serialization/example/portable_binary_oarchive.hpp> typedef portable_binary_oarchive test_oarchive; typedef std::ofstream test_ostream; #include <libs/serialization/example/portable_binary_iarchive.hpp> typedef portable_binary_iarchive test_iarchive; typedef std::ifstream test_istream; #define TEST_STREAM_FLAGS (std::ios_base::openmode)0 1. There is no "library_test" script in boost_1_64_0.tar.bz2. 2. cd boost_1_64_0/libs/serialization/test bjam -sBOOST_ARCHIVE_LIST=portable_binary_archive.hpp fails with many linking errors like that: ../../../bin.v2/libs/serialization/test/test_array_portable_binary_archive.test/gcc-6.3.0/debug/test_array.o: In function `portable_binary_oarchive::save(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)': /home/ss/src/boost_1_64_0/libs/serialization/test/../../../libs/serialization/example/portable_binary_oarchive.hpp:105: undefined reference to `boost::archive::basic_binary_oprimitive<portable_binary_oarchive, char, std::char_traits<char> >::save(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' What am i doing wrong? -- Best regards, Sergey Spiridonov GAMIC mbH, Roermonder Str. 151, 52072 Aachen, Germany Phone +49 241 889110 CEO Paul Malkomes Amtsgericht Aachen HRB 4029 VAT-ID: DE 121 677 540 Please use support(a)gamic.com for support requests and bug reports

1 0