Withdraw ASAP promise. Add note about comparisons between longs and

floats.
This commit is contained in:
Guido van Rossum 2001-07-26 16:49:34 +00:00
parent 090d6af630
commit 32a207d6aa
1 changed files with 7 additions and 3 deletions

View File

@ -16,11 +16,10 @@ Abstract
the C rationale for the numerical model is that it is very similar the C rationale for the numerical model is that it is very similar
to what happens at the hardware level, that rationale does not to what happens at the hardware level, that rationale does not
apply to Python. So, while it is acceptable to C programmers that apply to Python. So, while it is acceptable to C programmers that
2/3 == 0, it is surprising to Python programmers. 2/3 == 0, it is surprising to many Python programmers.
NOTE: in the light of recent discussions in the newsgroup, the NOTE: in the light of recent discussions in the newsgroup, the
motivation in this PEP (and details) need to be extended. I'll do motivation in this PEP (and details) need to be extended.
that ASAP.
Rationale Rationale
@ -120,6 +119,11 @@ Unresolved Issues
How do we deal with IEEE 754 operations? (probably, isnan/isinf should How do we deal with IEEE 754 operations? (probably, isnan/isinf should
be methods) be methods)
On 64-bit machines, comparisons between ints and floats may be
broken when the comparison involves conversion to float. Ditto
for comparisons between longs and floats. This can be dealt with
by avoiding the conversion to float. (Due to Andrew Koenig.)
Copyright Copyright