summaryrefslogtreecommitdiff
path: root/fma.c
diff options
context:
space:
mode:
authorvlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2008-07-19 17:31:41 +0000
committervlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2008-07-19 17:31:41 +0000
commit05e028523941a0393cdf50ff22715d77a07eb028 (patch)
treeb4e473f551e12c7e1e49e0ec786bb38c166ba0d2 /fma.c
parentabea9e7f276b764d8a8daaeb26c1e6fb88ad5fac (diff)
downloadmpfr-05e028523941a0393cdf50ff22715d77a07eb028.tar.gz
Merged changeset 5290 from the trunk (except tests/tests.c):
For the terminating null pointer of the functions mpfr_inits, mpfr_inits2, mpfr_clears, always use the type mpfr_ptr (no longer void *). Updated the description of these functions in the manual (mpfr.texi). The reason is that the C standard does not guarantee that (void *) 0 has the same representation as a null pointer to a structure (and even the same size). In most C implementations, the representations are the same, but one never knows (dynamical checking is also always possible)... git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/branches/2.3@5422 280ebfd0-de03-0410-8827-d642c229c3f4
Diffstat (limited to 'fma.c')
-rw-r--r--fma.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fma.c b/fma.c
index cd00abaf0..a8f617e84 100644
--- a/fma.c
+++ b/fma.c
@@ -174,7 +174,7 @@ mpfr_fma (mpfr_ptr s, mpfr_srcptr x, mpfr_srcptr y, mpfr_srcptr z,
{
MPFR_ASSERTN (zz != z);
MPFR_ASSERTN (0); /* TODO... */
- mpfr_clears (zo4, u, (void *) 0);
+ mpfr_clears (zo4, u, (mpfr_ptr) 0);
}
else
{