2010/1/30 <exar...@twistedmatrix.com> > On 10:55 pm, collinwin...@google.com wrote: > >> >> That people are directly munging CPython >> bytecode means that CPython should provide a better, more abstract way >> to do the same thing that's more resistant to these kinds of changes. >> > > It might be helpful to hear more about how the wordcode implementation > differs from the bytecode implementation. It's challenging to abstract from > a single data point. :) > > Jean-Paul
Wordcodes structure is simple. You can find information here<http://wpython2.googlecode.com/files/Beyond%20Bytecode%20-%20A%20Wordcode-based%20Python.pdf>. Slide 6 provide a description, 7 details about the structure and some examples. Slide 9 explains how I mapped most bytecodes grouping in 6 "families". However, wordcodes internals can be complicated to "pretty print", because they may carry many information. You can take a look at opcode.h<http://code.google.com/p/wpython2/source/browse/Include/opcode.h?repo=wpython10>and dis.py<http://code.google.com/p/wpython2/source/browse/Lib/dis.py?repo=wpython10>(function "common_disassemble") to understand why this happens. Cesare
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
