summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorvlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2007-12-12 14:46:26 +0000
committervlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2007-12-12 14:46:26 +0000
commitb662444cfbb02632f76ec72d5e321c02e68950be (patch)
tree2105d2e1365ec28599b7cd7d0169611418d8f919
parentbcfbf447709ba77151d05b50f2919ca3dffafd46 (diff)
downloadmpfr-b662444cfbb02632f76ec72d5e321c02e68950be.tar.gz
vasprintf.c: updated comment concerning the case nbchar > INT_MAX.
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@5068 280ebfd0-de03-0410-8827-d642c229c3f4
-rw-r--r--vasprintf.c6
1 files changed, 4 insertions, 2 deletions
diff --git a/vasprintf.c b/vasprintf.c
index 1331402f2..e75b46ce7 100644
--- a/vasprintf.c
+++ b/vasprintf.c
@@ -1105,8 +1105,10 @@ mpfr_vasprintf (char **ptr, const char *fmt, va_list ap)
number of bytes needed to hold the output excluding the
terminating null is greater than {INT_MAX}." See:
http://www.opengroup.org/onlinepubs/009695399/functions/fprintf.html
- So, I (VL) propose that we should return a negative value and
- set the erange flag. */
+ But it doesn't say anything concerning the other printf-like
+ functions. A defect report has been submitted to austin-review-l
+ (item 2532). So, for the time being, I (VL) propose that we should
+ return a negative value and set the erange flag. */
MPFR_ASSERTN (nbchar <= INT_MAX);
return (int) nbchar;
}