[Python-Dev] Possible optimization for LOAD_FAST ? (original) (raw)
Cesare Di Mauro cesare.di.mauro at gmail.com
Fri Dec 31 18:42:53 CET 2010
- Previous message: [Python-Dev] Possible optimization for LOAD_FAST ?
- Next message: [Python-Dev] Possible optimization for LOAD_FAST ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2010/12/31 Ethan Furman <ethan at stoneleaf.us>
Cesare Di Mauro wrote:
>
2010/12/29 "Martin v. Löwis" wrote: >> Am 28.12.2010 18:08, schrieb Lukas Lueg:
Also, the loadfast in lne 22 to reference x could be taken out of the >>> loop as x will always point to the same object.... That's not true; a debugger may change the value of x. Another example. I can totally remove the variable i, just using the stack, so a debugger (or, in general, having the tracing enabled) cannot even find something to change about it. -1 Debugging is challenging enough as it is -- why would you want to make it even more difficult?
Ethan
With a good test suite you can forget debuggers.
In more than 6 years of Python programming, I have used it only two times (to debug an ANTLR generated parser).
Cesare -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20101231/91cb7a02/attachment.html>
- Previous message: [Python-Dev] Possible optimization for LOAD_FAST ?
- Next message: [Python-Dev] Possible optimization for LOAD_FAST ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]