summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorvlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2015-05-29 08:54:33 +0000
committervlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2015-05-29 08:54:33 +0000
commitb8b853306f903fe8e2806a3ed29fb7fa53b31f34 (patch)
tree25c17749f60f1eedc84affb1cad9d7b63247d3c2 /doc
parentc73d5d6d548ad99ada57b507e1ea19a7bcfbb519 (diff)
downloadmpfr-b8b853306f903fe8e2806a3ed29fb7fa53b31f34.tar.gz
[doc/mpfr.texi] Added a remark concerning the mpfr_rint_* functions.
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@9469 280ebfd0-de03-0410-8827-d642c229c3f4
Diffstat (limited to 'doc')
-rw-r--r--doc/mpfr.texi5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/mpfr.texi b/doc/mpfr.texi
index 82a1649fa..25dd7e039 100644
--- a/doc/mpfr.texi
+++ b/doc/mpfr.texi
@@ -2610,7 +2610,10 @@ mathematical function).
Contrary to @code{mpfr_rint}, those functions do perform a double rounding:
first @var{op} is rounded to the nearest integer in the direction given by
the function name, then this nearest integer (if not representable) is
-rounded in the given direction @var{rnd}.
+rounded in the given direction @var{rnd}. Thus these round-to-integer
+functions behave more like the other mathematical functions, i.e., the
+returned result is the correct rounding of the exact result of the function
+in the real numbers.
For example, @code{mpfr_rint_round} with rounding to nearest and a precision
of two bits rounds 6.5 to 7 (halfway cases away from zero), then 7 is
rounded to 8 by the round-even rule, despite the fact that 6 is also