#8896: 0.0000000000000000000000000000 is parsed completely differently than
1.0000000000000000000000000000 for no good reason
--------------------------------+-------------------------------------------
Reporter: was | Owner: AlexGhitza
Type: defect | Status: needs_review
Priority: minor | Milestone: sage-4.4.3
Component: basic arithmetic | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
--------------------------------+-------------------------------------------
Comment(by leif):
Replying to [comment:9 robertwb]:
> Replying to [comment:6 leif]:
> > But currently, ''leading'' zeros contribute to the precision, too: :)
> > {{{
> > sage: RealNumber(0.000000000000000000).prec()
> > 67
> > sage: RealNumber(00.000000000000000000).prec()
> > 70
> > sage: RealNumber(.000000000000000000).prec()
> > 64
> > }}}
> > I'm not sure if this is intentional, it's at least uncommon.
>
> That's the point of this ticket. For 0, all zeros are leading.
Not really. We were (only I think) considering zeros of the
'''fractional''' part.
Truncation only makes sense from the right; and you don't express
precision by padding zeros to the left. Stating that the earth's diameter
is about 013 million meters doesn't give more information than stating it
is about 13 million meters.
> Updated the docstring a bit. This is mostly for use by the preparser,
though of course it gets used directly as well.
I was thinking of scientific notation syntax, too. (Also the examples do
not contain that form.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8896#comment:13>
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.
