diff options
| author | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2010-05-31 13:44:36 +0000 |
|---|---|---|
| committer | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2010-05-31 13:44:36 +0000 |
| commit | cdad2acbe0da3646040d2e29c9710f212942a717 (patch) | |
| tree | f131bbbb5182e942ed046e195304d8c29a79e01a | |
| parent | 5ce6d2679a25cc942a421c76f6e045addeec64ca (diff) | |
| download | mpfr-cdad2acbe0da3646040d2e29c9710f212942a717.tar.gz | |
[mpfr.texi, NEWS] Update related to r6879: "Made defined the previously
undefined cases of mpfr_get_si, mpfr_get_ui, mpfr_get_sj, mpfr_get_uj,
mpfr_get_z and mpfr_get_z_2exp. In such cases, the erange flag is set.".
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@6893 280ebfd0-de03-0410-8827-d642c229c3f4
| -rw-r--r-- | NEWS | 4 | ||||
| -rw-r--r-- | mpfr.texi | 15 |
2 files changed, 19 insertions, 0 deletions
@@ -48,6 +48,10 @@ Changes from versions 2.4.* to version 3.0: - mpfr_strtofr now accepts bases from 37 to 62. - mpfr_custom_get_mantissa was renamed to mpfr_custom_get_significand (mpfr_custom_get_mantissa is still available via a #define). +- Functions mpfr_get_si, mpfr_get_ui, mpfr_get_sj, mpfr_get_uj, + mpfr_get_z and mpfr_get_z_2exp no longer have cases with undefined + behavior; in these cases, the behavior is now specified, and in + particular, the erange flag is set. - New functions mpfr_buildopt_tls_p and mpfr_buildopt_decimal_p giving information about options used at MPFR build time. - New function mpfr_regular_p. @@ -3261,6 +3261,11 @@ This function was returning zero, except for NaN and Inf, which do not exist in MPF. The @emph{erange} flag is now set in these cases, and @code{mpfr_get_f} now returns the usual ternary value. +@item @code{mpfr_get_si}, @code{mpfr_get_sj}, @code{mpfr_get_ui} +and @code{mpfr_get_uj} changed in MPFR 3.0. +In previous MPFR versions, the cases where the @emph{erange} flag +is set were unspecified. + @item @code{mpfr_get_z} changed in MPFR 3.0. The return type was @code{void}; it is now @code{int}, and the usual ternary value is returned. Thus programs that need to work with both @@ -3285,6 +3290,16 @@ as in: Alternatively, @code{if ... else} can be used instead of the conditional operator. +Moreover the cases where the @emph{erange} flag is set were unspecified +in MPFR 2.x. + +@item @code{mpfr_get_z_exp} changed in MPFR 3.0. +In previous MPFR versions, the cases where the @emph{erange} flag +is set were unspecified. +Note: this function has been renamed to @code{mpfr_get_z_2exp} +in MPFR 3.0, but @code{mpfr_get_z_exp} is still available for +compatibility reasons. + @item @code{mpfr_strtofr} changed in MPFR 2.3.1 and MPFR 2.4. This was actually a bug fix since the code and the documentation did not match. But both were changed in order to have a more consistent |