[Python-Dev] INPLACE_ADD and INPLACE_MULTIPLY oddities in ceval.c (original) (raw)
Guido van Rossum guido at python.org
Thu Mar 30 06:24:55 CEST 2006
- Previous message: [Python-Dev] INPLACE_ADD and INPLACE_MULTIPLY oddities in ceval.c
- Next message: [Python-Dev] INPLACE_ADD and INPLACE_MULTIPLY oddities in ceval.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 3/29/06, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Tim Hochberg wrote:
> Still, perhaps for Py3K it's worth considering > if PyNumberInplaceAdd should only call iadd and add, not > radd. Thus giving the target object complete control during inplace > adds. That's probably reasonable, although it would break the conceptual notion that a += b is equivalent to a = a + b when a can't be modified in-place.
No, it's not reasonable, because this would fail:
x = 5 x += 0.5
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] INPLACE_ADD and INPLACE_MULTIPLY oddities in ceval.c
- Next message: [Python-Dev] INPLACE_ADD and INPLACE_MULTIPLY oddities in ceval.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]