summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorvlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2012-12-12 10:35:20 +0000
committervlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2012-12-12 10:35:20 +0000
commitd89dafd79868dc6f2a2df72ebfd85deb7178bf45 (patch)
tree23d3bf4d95d80aee269b50780db2c4dce7d5daea
parent6f9530a5d4bea1e7a085d51ad7d97459b5e8fa97 (diff)
downloadmpfr-d89dafd79868dc6f2a2df72ebfd85deb7178bf45.tar.gz
[src/fpif.c] Added a FIXME comment in mpfr_fpif_import concerning the
precision. git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@8437 280ebfd0-de03-0410-8827-d642c229c3f4
-rw-r--r--src/fpif.c7
1 files changed, 6 insertions, 1 deletions
diff --git a/src/fpif.c b/src/fpif.c
index 87b1442f7..c12322d34 100644
--- a/src/fpif.c
+++ b/src/fpif.c
@@ -543,8 +543,13 @@ mpfr_fpif_import (mpfr_t x, FILE *fh)
unsigned char *buffer;
size_t used_size;
+ /* FIXME: One may have precision > MPFR_PREC_MAX. This can be taken into
+ account either here or in mpfr_fpif_read_precision_from_file. One may
+ also have 0 < precision < MPFR_PREC_MIN. Should this be regarded as an
+ error or should the precision of the number be raised to MPFR_PREC_MIN
+ (I think that the latter choice is safe and expected). */
precision = mpfr_fpif_read_precision_from_file (fh);
- if (precision == 0)
+ if (precision == 0) /* precision = 0 means an error */
return -1;
mpfr_set_prec (x, precision);