[Python-Dev] Keep default comparisons - or add a second set? (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Tue Dec 20 02:37:06 CET 2005
- Previous message: [Python-Dev] Keep default comparisons - or add a second set?
- Next message: [Python-Dev] Keep default comparisons - or add a second set?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Jewett wrote:
Or, at the very least, promote a standard way to say "just get me a canonical ordering of some sort"
That would be my preference. Comparison for canonical ordering should be a distinct operation with its own spelling. Then Guido's
Comparisons other than == and != between disparate types will raise an exception unless explicitly supported by the type
can be true without precluding the existence of a canonical ordering.
-- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg.ewing at canterbury.ac.nz +--------------------------------------+
- Previous message: [Python-Dev] Keep default comparisons - or add a second set?
- Next message: [Python-Dev] Keep default comparisons - or add a second set?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]