On Tue, 19 Nov 2013 19:51:10 +0100 Antoine Pitrou <solipsis at pitrou.net> wrote: > On Mon, 18 Nov 2013 16:48:05 -0800 > Guido van Rossum <guido at python.org> wrote: > > > > Food for thought: maybe we should have variable-encoding lengths for all > > opcodes, rather than the current cumbersome scheme? > > Well, it's not that cumbersome... If you look at CPU encodings, they > also tend to have different opcodes for different immediate lengths. > > In your case, I'd say it mostly leads to a bit of code duplication. But > the opcode space is far from exhausted right now :) Oops... Make that "in our case", of course. cheers Antoine.
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