#16127: Fix comparison of PARI objects
-------------------------------------+-------------------------------------
Reporter: pbruin | Owner:
Type: defect | Status: needs_review
Priority: critical | Milestone: sage-6.4
Component: interfaces | Resolution:
Keywords: pari comparison | Merged in:
Authors: Peter Bruin | Reviewers: Jeroen Demeyer
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/ticket/16127 | 12fbcad65c6438fe0495c3b2424468f24b49a9ee
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by pbruin):
By the way, I think that we should in the end (but on a different ticket)
get rid of `gcmp_string()` and make `_cmp_c_impl()` a wrapper for PARI's
`cmp_universal()`. This is faster and defines a total ordering, while
being mathematically no more or less sensible than string comparison. As
far as I know, once you have the rich comparison operators, the only real
remaining use for `cmp()` is sorting arbitrary lists; there is probably no
strong reason why it should be compatible with the individual comparison
operators.
--
Ticket URL: <http://trac.sagemath.org/ticket/16127#comment:19>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
