From: Hal Fulton <hal9000@...>
Date: 2004-01-17T04:09:34+09:00
Subject: Re: ruby-dev summary 22435-22573

George Marrows wrote:
> It's a very similar approach to ByteCodeRuby
> (http://rubyforge.org/projects/bytecoderuby/), which also works as a
> Ruby extension. BCR needs to patch Ruby slightly though - I'm
> impressed Sasada-san has managed to avoid this so far.
> 
> On the plus side, BCR is much further advanced, with most of the Ruby
> language implemented (the big things missing are retry, eval, threads
> and various set_trace_func-style callbacks). It also has 650+ tests to
> ensure that its results match Ruby's. The next BCR release (probably
> in 4-6 weeks) should be self-hosting - BCR will be capable of running
> its own compilation code (which is written in Ruby) and supporting
> libraries (Ruth and Test::Unit).

[snippage]

I'm extremely lazy when it comes to reading docs embedded inside .tgz
files -- I'd much rather see docs on the web.

How good are the docs, anyway? I'm especially interested in your
choice of opcodes and such. Is it practical to write an assembler
for your VM? Have you perhaps already done it?

Hal