Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Why is there no post-pre increment operator in python

21 views
Skip to first unread message

riteshti...@gmail.com

unread,
Jan 12, 2006, 10:32:36 PM1/12/06
to
Anyone has any idea on why is there no post/pre increment operators in
python ?
Although the statement:
++j
works but does nothing

Roy Smith

unread,
Jan 12, 2006, 10:40:00 PM1/12/06
to
riteshti...@gmail.com wrote:
> Anyone has any idea on why is there no post/pre increment operators in
> python ?

Short answer: Because Guido didn't like them.

Longer answer: Because they encourage people to write cryptic one-liners.
There really isn't anything you can't write with them that you couldn't
write just as well without them. It just takes another line or two of
code. The end result may be a little longer, but it's almost always easier
to understand.

> Although the statement:
> ++j
> works but does nothing

Well, it works in the sense that it's not a syntax error, but it doesn't
quite do nothing. It applies the unary + operator to the value of j, then
does it again, then throws away the result. Granted, that's probably not
what you expected, and probably not very useful, but it's not quite
"nothing".

Tim Peters

unread,
Jan 12, 2006, 10:57:10 PM1/12/06
to pytho...@python.org
[riteshti...@gmail.com]

> Anyone has any idea on why is there no post/pre increment operators in
> python ?

Maybe because Python doesn't aim at being a cryptic portable assembly
language? That's my guess ;-)

> Although the statement:
> ++j
> works but does nothing

That depends on the type of j, and how it implements the __pos__()
method. The builtin numeric types (integers, floats, complex)
implement __pos__ to return the base-class part of `self`. That's not
the same as doing nothing. There is no "++" operator in Python, BTW
-- that's two applications of the unary-plus operator.

>>> class MyFloat(float):
... pass
>>> x = MyFloat(3.5)
>>> x
3.5
>>> type(x)
<class '__main__.MyFloat'>
>>> type(+x) # "downcasts" to base `float` type
<type 'float'>
>>> type(x.__pos__()) # same thing, but wordier
<type 'float'>

If you want, you can implement __pos__ in your class so that

+a_riteshtijoriwala_object

posts messages to comp.lang.c asking why C is so inflexible ;-).

Mike Meyer

unread,
Jan 12, 2006, 11:15:58 PM1/12/06
to
riteshti...@gmail.com writes:
> Anyone has any idea on why is there no post/pre increment operators in
> python ?

For lots of good reasons.

> Although the statement:
> ++j
> works but does nothing

So does --j. They both parse as a value with two unary operators
applied to it in succession: +(+(j)) and -(-(j)).

<mike
--
Mike Meyer <m...@mired.org> http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

gene tani

unread,
Jan 13, 2006, 4:23:40 AM1/13/06
to

"+=1" and "-=1" inflate your KLOC by .001, but they always work as
expected with integers, it's when you do augmented assignments on lists
and tuples that shit happens

http://zephyrfalcon.org/labs/python_pitfalls.html

Peter Hansen

unread,
Jan 13, 2006, 6:57:19 AM1/13/06
to pytho...@python.org

The reason is pretty complex, but here it is: Python is not C.

-Peter

Roy Smith

unread,
Jan 13, 2006, 8:54:15 AM1/13/06
to
In article <1137144220.3...@g43g2000cwa.googlegroups.com>,
"gene tani" <gene...@gmail.com> wrote:

> http://zephyrfalcon.org/labs/python_pitfalls.html

Thanks for posting that URL; I hadn't seen the list before. Skimming over
it, none of them really seemed noteworthy until I got to "5. Mutable
default arguments", which rather shocked me. Good stuff to know!

gene tani

unread,
Jan 13, 2006, 11:33:07 AM1/13/06
to

Peter Hansen

unread,
Jan 13, 2006, 11:53:56 AM1/13/06
to pytho...@python.org
gene tani wrote:

> Roy Smith wrote:
>>Thanks for posting that URL; I hadn't seen the list before.
[...]

>
> pls don't hijack threads

Um, he didn't "hijack" it, he follow a tangent to the discussion and
even changed the Subject line in a very appropriate manner, both of are
completely acceptable netiquette and long-standing Usenet practices.

(Rather like I'm doing here.)

-Peter

Fredrik Lundh

unread,
Jan 13, 2006, 12:04:54 PM1/13/06
to pytho...@python.org
"gene tani" wrote:

> pls don't hijack threads

this is usenet, not gene tani's web board.

if you have trouble dealing with subthreads, get a better news reader.

</F>

gene tani

unread,
Jan 13, 2006, 12:36:03 PM1/13/06
to

Sorry, I was trying to be helpful. One thing, i think it helps to
glance over rejected PEPs every once in a while to reinforce what's not
there
http://www.python.org/peps/

>
> -Peter

Gene

0 new messages