I think you're misunderstanding the idea of YARV and ruby2c.  They
aren't forks of Ruby.  YARV is a VM for Ruby which is likely to become
part of Ruby 2.0.  YARV works with your existing Ruby code (except for
unimplemented features, like continuations), and ruby2c is simply a
program that converts Ruby code into C.  There's no forking going on,
and Matz's Ruby is still the one and only Ruby implementation.

Bill

On Fri, 4 Feb 2005 08:28:42 +0900, Navindra Umanee
<navindra / cs.mcgill.ca> wrote:
> Alexander Kellett <ruby-lists / lypanov.net> wrote:
> > maybe its just me but i expected *many* more emails in
> > reply to the yarv and ruby2c releases!!!!!
> 
> I'm not sure what you're talking about.
> 
> Where is the YARV announcement/release on this list?  I certainly
> haven't seen it.  I saw a yarv/db thread but that was it.  YARV looks
> and sounds very interesting though.  I just don't have a project to
> run on it yet...  when I do I'll make noise. :-)
> 
> ruby2c seems a very specialised thing.  I mean sure, it's nearly 1.0.0
> but nobody seems really sure what to do with it given the limitations
> which are apparently by design.
> 
> Anyway, as a newcomer, I'm sure I don't know what to make of all this.
> What about the official Ruby release and VM?  Seems to be a lot of
> forking going on.
> 
> Cheers,
> Navin.
> 
> 


-- 
$stdout.sync = true
"Just another Ruby hacker.".each_byte do |b|
  ('a'..'z').step do|c|print c+"\b";sleep 0.007 end;print b.chr
end; print "\n"