diff options
author | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2008-07-19 17:31:41 +0000 |
---|---|---|
committer | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2008-07-19 17:31:41 +0000 |
commit | 05e028523941a0393cdf50ff22715d77a07eb028 (patch) | |
tree | b4e473f551e12c7e1e49e0ec786bb38c166ba0d2 /sub1sp.c | |
parent | abea9e7f276b764d8a8daaeb26c1e6fb88ad5fac (diff) | |
download | mpfr-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 'sub1sp.c')
-rw-r--r-- | sub1sp.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -64,7 +64,7 @@ int mpfr_sub1sp (mpfr_ptr a, mpfr_srcptr b, mpfr_srcptr c, mp_rnd_t rnd_mode) inexact, inexact2); MPFR_ASSERTN (0); } - mpfr_clears (tmpa, tmpb, tmpc, (void *) 0); + mpfr_clears (tmpa, tmpb, tmpc, (mpfr_ptr) 0); return inexact; } # define mpfr_sub1sp mpfr_sub1sp2 |