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

Michael Letterle michael.letterle at gmail.com
Sun Jan 17 22:00:04 EST 2010

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> 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?
> http://parsetree.rubyforge.org/
> 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.
> ~Jimmy
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core

Michael Letterle
IronRuby MVP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20100117/40faf560/attachment-0001.html>

More information about the Ironruby-core mailing list