Bob Ippolito <bob at redivi.com>: > Doing extensive checking of bytecode at runtime would make Python's > interpreter much slower than it already is. Another approach would be to make the bytecode a special object that can only be created by the compiler (or other C code). If you wanted custom bytecode, you'd have to build an AST and feed it to the compiler, or write an extension module. No doubt some bytecode hackers would find this too limiting, however. Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg at cosc.canterbury.ac.nz +--------------------------------------+
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