#8896: 0.0000000000000000000000000000 is parsed completely differently than
1.0000000000000000000000000000 for no good reason
--------------------------------+-------------------------------------------
Reporter: was | Owner: AlexGhitza
Type: defect | Status: needs_info
Priority: minor | Milestone: sage-4.7.1
Component: basic arithmetic | Keywords:
Work_issues: | Upstream: N/A
Reviewer: Mariah Lenox | Author: Robert Bradshaw
Merged: | Dependencies:
--------------------------------+-------------------------------------------
Comment(by kcrisman):
Another argument is that the BDFL suggested this change fairly strongly
when opening this ticket :)
More seriously, I do have a question here.
Robert's reasoning seems sound in the following example - we want a high-
precision zero, and this is the best way to acquire it.
{{{
> sage: (0.000000000000000000000).prec()
> 77
> sage: (0.000000000000000000001).prec()
> 53
}}}
But I agree with Jeroen that the following seems problematic. Didn't you
say yourself (robertwb) that leading zeros ''before'' the decimal point
shouldn't make a difference? So in the case here maybe we should have the
default precision...
{{{
> sage: (000000000000000000000.0).prec()
> 77
> sage: (000000000000000000000.1).prec()
> 53
}}}
Keeping in mind that I have very little invested in either outcome for
now, so take these only as observations.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8896#comment:27>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
