4 ms·
Actually, his take on it isn't quite accurate. It's not "written in C++". From http://rubini.us http://rubini.us : Wherever possible Rubinius is written in R
by daveungerer 16y ago
Actually, his take on it isn't quite accurate. It's not "written in C++".
From http://rubini.us http://rubini.us :
Wherever possible Rubinius is written in Ruby. Where not possible (yet), it's C++.
And further down:
The Rubinius bytecode virtual machine is written in C++, incorporating LLVM to compile bytecode to machine code at runtime. The bytecode compiler and vast majority of the core classes are written in pure Ruby.
So, it's the VM that's C++. The bytecode compiler (which is technically what's meant by "interpreter" in this case) is ruby.
- evanphx 16y agoWell, not exactly. The interpreter is in C++. By bytecode compiler he means the code that translates from a ruby AST into bytecode, which is in ruby.
- daveungerer 16y agoSure, but the point I'm trying to make is that Wayne Seguin was using the word "interpreter" colloquially to refer to the whole program, in effect saying that the whole code base is C++.