mpf: which bug should we correct? (doc or code)

bodrato at bodrato at
Mon Jun 2 11:15:21 UTC 2014


Il Lun, 2 Giugno 2014 10:04 am, Andreas Enge ha scritto:
> On Sun, Jun 01, 2014 at 08:20:19AM +0200, bodrato at wrote:
>> Now the problem is: what do we want (and should we test) from mpf
>> functions?
> Instead of re-implementing mpfr, an easy fix would be to simply drop mpf

"simply" breaking backward compatibility is easy on our side, but it may
be not on users side...
Of course I agree, there is no need to (re-)implement correct rounding.
The best fix probably is to relax the claim in the documentation...

> from gmp and refer people to mpfr...

We usually do. I mean, people asking for floating-point operations on GMP
lists usually get a "look at MPFR" answer.
Also the manual of GMP refers to MPFR for "well-defined precision and
accurate rounding".



More information about the gmp-devel mailing list