- Boost-users - lists.boost.org

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