Imported Upstream version 1.72.0

[platform/upstream/boost.git] / libs / math / doc / concepts / concepts.qbk

diff --git a/libs/math/doc/concepts/concepts.qbk b/libs/math/doc/concepts/concepts.qbk
index 845b67a..6cff42e 100644 (file)
--- a/libs/math/doc/concepts/concepts.qbk
+++ b/libs/math/doc/concepts/concepts.qbk
@@ -140,7 +140,8 @@ and which forward to the libquadmath equivalents.
 
 Ultimately these facilities should be provided by GCC and `libstdc++`.
 
-[endsect]
+[endsect] [/section:float128 Using with GCC's __float128 datatype]
+
 
 [section:use_mpfr Using With MPFR or GMP - High-Precision Floating-Point Library]
 
@@ -192,11 +193,6 @@ Alternatively use with `mpreal` would look like:
       std::cout << std::setprecision(50) << v << std::endl;
    }
 
-For those functions that are based upon the __lanczos, the bindings
-defines a series of approximations with up to 61 terms and accuracy
-up to approximately 3e-113.  This therefore sets the upper limit for accuracy
-to the majority of functions defined this library when used with either `mpfr_class` or `mpreal`.
-
 There is a concept checking test program for mpfr support
 [@../../../../libs/math/test/mpfr_concept_check.cpp here] and
 [@../../../../libs/math/test/mpreal_concept_check.cpp here].
@@ -458,7 +454,7 @@ and then specialise `lanczos_traits` for type T.  Otherwise you may have to hack
 [@../../tools/lanczos_generator.cpp
 libs/math/tools/lanczos_generator.cpp] to find a suitable
 approximation for your RealType.  The code will still compile if you don't do
-this, but both accuracy and efficiency will be greatly compromised in any
+this, but both accuracy and efficiency will be somewhat compromised in any
 function that makes use of the gamma\/beta\/erf family of functions.
 
 [endsect] [/section:real_concepts Conceptual Requirements for Real Number Types]
@@ -625,7 +621,7 @@ The class template `DistributionConcept` verifies the existence
 required by the [link math_toolkit.dist_concept Distribution concept].
 These are checked by calls like
 
-v = pdf(dist, x); // (Result v is ignored).
+  v = pdf(dist, x); // (Result v is ignored).
 
 And in addition, those that accept two arguments do the right thing when the
 arguments are of different types (the result type is always the same as the