Hi Clifford,
this is all good to hear. You took over from Nathan right ? Good on you,
and thanks to both of you.
So if you know him, he may be interested to hear that his old dream may
still come true and it's not too late to join:-)
I also like the idea of extensible languages, and the fact that people
experiment with them. It would be very nice to have a solid base for
that, so not everyone would always have to write a new vm just to get
a small twist onto a language. And anyway, we should all be nicer to our
neighbours and accept other oo languages. Work together .... but this
is phase two of my already 10year plan.
btw: i am not writing an interpreter, but a vm. I produce binary machine
code from ruby. And the idea is that the vm will be such a binary that
implements ruby syntax and libraries, on top of a general core (that may
also
implement python or java/script). The vm would jit the new code, in much
the same way that i now compile it. (so if it's not faster than mri i
have done something very wrong :-)
*
There is no c involved (no compiler/llvm, no libraries, not even libc),
so i have obviously taken the long road. But i am old enough not to be
in a hurry, and found that in life direction is much more important than
speed.
As to the tests, i sort of agree, but needed to see that my stuff works,
before actually checking that it also is correct ruby. One can see them
as unit tests.
Eventually i will go the (is it) mspec way, but for now (before i
achieve bootstrap) i am happy with a sensible subset.
Torsten
* 'cause i'm happy to talk about the vm at any length, but it is off
topic so i won't here.
https://github.com/salama