#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:
--------------------------------+-------------------------------------------
Changes (by jdemeyer):
* status: positive_review => needs_info
Comment:
In my opinion, this ticket is a huge can of worms and a bad idea. I don't
see any mathematically consistent reason who 0.0 '''should''' be treated
differently than 0.0000000000000.
I really think the current behaviour of Sage is what makes the most sense
(mathematically) so I am not in favour of this ticket. Of course, if the
majority thinks this patch is a good idea then I'm all for it.
One thing about the patch which is very unclear is why zero is treated
differently from other numbers. Consider::
{{{
sage: (0.0).prec()
53
sage: (0.1).prec()
53
sage: (000000000000000000000.0).prec()
77
sage: (000000000000000000000.1).prec()
53
sage: (0.000000000000000000000).prec()
77
sage: (0.000000000000000000001).prec()
53
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8896#comment:25>
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.
