[Ironruby-core] Bug?: Ruby2Ruby and ParseTree on IronRuby

Jim Deville jdeville at microsoft.com
Mon Jan 18 00:25:31 EST 2010

ParseTree is actually already implemented for IronRuby. Tomas did that to get merb running last year. Ruby2Ruby will probably need some work though.

From: Michael Letterle <michael.letterle at gmail.com>
Sent: Sunday, January 17, 2010 7:01 PM
To: ironruby-core at rubyforge.org <ironruby-core at rubyforge.org>
Subject: Re: [Ironruby-core] Bug?: Ruby2Ruby and ParseTree on IronRuby

Considering we have access to the AST.. I would think that.. in theory at least, it would be EASIER to implement than CRuby...

But yeah, what Jimmy said :)

On Sun, Jan 17, 2010 at 9:32 PM, Jimmy Schementi <Jimmy.Schementi at microsoft.com<mailto:Jimmy.Schementi at microsoft.com>> wrote:
> Any ideas on this? It's using Ruby2Ruby and ParseTree. Is it because it's
> based around C extensions? Anyone know how to do it on the CLR?


ParseTree hooks into MRI's internals and exposes the parse tree for a given chunk of Ruby code. For this to work on IronRuby you'd have to rewrite the C-extension-portion of this library to look at the DLR trees (may require changes to ironruby as well to expose the tree, but I'm not sure).

Ruby2Ruby is just a Ruby parser written in Ruby, but depends on racc, which uses a C extension, though it seems like you can run racc without it.

Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>

Michael Letterle
IronRuby MVP

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20100118/29e5ec11/attachment.html>

More information about the Ironruby-core mailing list