update source to Ceph Pacific 16.2.2

[ceph.git] / ceph / src / boost / boost / math / special_functions / round.hpp

diff --git a/ceph/src/boost/boost/math/special_functions/round.hpp b/ceph/src/boost/boost/math/special_functions/round.hpp
index 71439a6f6bd87b22eb647c0c2c64cad18e23cd6a..9f07105f1cc25ea00b2dbf0504201893f8f1e3b1 100644 (file)
--- a/ceph/src/boost/boost/math/special_functions/round.hpp
+++ b/ceph/src/boost/boost/math/special_functions/round.hpp
@@ -20,7 +20,7 @@ namespace boost{ namespace math{
 namespace detail{
 
 template <class T, class Policy>
-inline typename tools::promote_args<T>::type round(const T& v, const Policy& pol, const mpl::false_)
+inline typename tools::promote_args<T>::type round(const T& v, const Policy& pol, const boost::false_type&)
 {
    BOOST_MATH_STD_USING
       typedef typename tools::promote_args<T>::type result_type;
@@ -52,7 +52,7 @@ inline typename tools::promote_args<T>::type round(const T& v, const Policy& pol
    }
 }
 template <class T, class Policy>
-inline typename tools::promote_args<T>::type round(const T& v, const Policy&, const mpl::true_)
+inline typename tools::promote_args<T>::type round(const T& v, const Policy&, const boost::true_type&)
 {
    return v;
 }
@@ -62,7 +62,7 @@ inline typename tools::promote_args<T>::type round(const T& v, const Policy&, co
 template <class T, class Policy>
 inline typename tools::promote_args<T>::type round(const T& v, const Policy& pol)
 {
-   return detail::round(v, pol, mpl::bool_<detail::is_integer_for_rounding<T>::value>());
+   return detail::round(v, pol, boost::integral_constant<bool, detail::is_integer_for_rounding<T>::value>());
 }
 template <class T>
 inline typename tools::promote_args<T>::type round(const T& v)
@@ -71,7 +71,7 @@ inline typename tools::promote_args<T>::type round(const T& v)
 }
 //
 // The following functions will not compile unless T has an
-// implicit convertion to the integer types.  For user-defined
+// implicit conversion to the integer types.  For user-defined
 // number types this will likely not be the case.  In that case
 // these functions should either be specialized for the UDT in
 // question, or else overloads should be placed in the same