On Oct 26, 2006, at 10:23 , William Stein wrote:
> > On Thu, 26 Oct 2006 06:51:42 -0500, Bill Hart <[EMAIL PROTECTED]> > wrote: > >> >> But it returns the answer in decimal, not binary, and the answer is >> incorrect, in some cases not just to one, but to two decimal places. >> >> I have read the MPFR manual, in detail, and I understand their model >> and why it is useful, but I find it confusing to output the incorrect >> decimal expression in SAGE. > > SAGE could internally compute with a few more digits of precision > than requested, and always output numbers with the last few digits > truncated. Would that be less confusing? I believe that this is the way the IEEE floating point standard (which is implemented as 'native' floating point by most chips today) does it: more bits are computed; only the promised bits are displayed. Justin -- Justin C. Walker, Curmudgeon-at-Large () The ASCII Ribbon Campaign /\ Help Cure HTML Email --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
