RetroSearch Browse

Thu Jul 8 18:01:31 CEST 2004 · http://mail.python.org/pipermail/python-dev/2004-July/045985.html

> I'm really not even proposing a change to Python as much as trying
> to understand why it is the way it is. I can see how a stack is
> helpful for evaluating deeply nested expressions (although temporary
> variables seems another good valid approach). I just don't see the
> payoff for shuffling variables from locals onto the stack and back
> into the locals table.

To minimize the instruction set and simplify the compiler.  You'll
need the most general operation (return from stack) anyway.

--Guido van Rossum (home page: http://www.python.org/~guido/)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2004-July/045985.html below:

[Python-Dev] Why is Bytecode the way it is?