On 11/9/05, Guido van Rossum <guido at python.org> wrote: > > > I like Phillip's suggestion -- no new opcode, just a conditional jump > > > that can be easily optimized out. > > > > Huh? But Phillip is suggesting a new opcode that is essentially the > > same as my proposal but naming it differently and saying the bytecode > > should get changed directly instead of having the eval loop handle the > > semantic differences based on whether -O is being used. > > Sorry. No problem. Figured you just misread mine. > Looking back they look pretty much the same to me. Somehow I > glanced over Phillip's code and thought he was proposing to use a > regular JUMP_IF opcode with the special __debug__ variable (which > would be a 3rd possibility, good if we had backwards compatibility > requirements for bytecode -- which we don't, fortunately :-). > Fortunately. =) So does this mean you like the idea? Should this all move forward somehow? -Brett
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4