3 ms·
It's very different to use the PyPy toolchain that is to run on JVM or .NET. It does not reuse any bit of the Python VM, but uses RPython as the implementation
by fijal 14y ago
It's very different to use the PyPy toolchain that is to run on JVM or .NET. It does not reuse any bit of the Python VM, but uses RPython as the implementation language. You don't share bytecode, you don't share objectmodel. You share the garbage collector and you generate the JIT for your language (unlike reusing the existing one).
- SoftwareMaven 14y agoThis is one of the most fascinating things about PyPy, and one least understood (most likely because the primary output of the PyPy interpreter generator happens to be a Python interpreter written in a static language much like Python called RPython). I've been toying with the idea of building a little language, just for fun. The mess of building an interpreter has always kept me from it, but as I've spent some time looking at PyPy, I think I might just have a go.