Er, to be clear, this just seems to be an interpreter -- not a meta circular interpreter. I don't see any evidence that it is able to evaluate its own definitions or its own API. It doesn't have any tools to handle class definitions, object instantiation, or method invocation, so I'm not sure by what definition of "meta circular" this interpreter fits.
Not trying to knock the project. Very cool code! Just don't understand how it qualifies as a "meta circular".
In contrast, my Metascala JVM (https://github.com/lihaoyi/Metascala) is indeed metacircular, and can interpret itself 1 and 2 layers deep (each layer 100x slower than the layer before!)
pytype (https://github.com/google/pytype) is based on symbolic interpretation of python bytecode, but with the data stack storing types rather than values. it works very well and has been running in production within google forever.
the nice thing about writing a bytecode rather than an AST interpreter is that you can leverage a lot of the work the python compiler does, and work with the resulting simplified code.
Somewhat similar: My PyCPython project (https://github.com/albertz/PyCPython), where I wrote a C interpreter in Python, and then tried to interpret CPython. I never really completed this project though.
Not trying to knock the project. Very cool code! Just don't understand how it qualifies as a "meta circular".
reply