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.lette...@gmail.com> Sent: Sunday, January 17, 2010 7:01 PM To: ironruby-core@rubyforge.org <ironruby-core@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.scheme...@microsoft.com<mailto:jimmy.scheme...@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@rubyforge.org<mailto:Ironruby-core@rubyforge.org> http://rubyforge.org/mailman/listinfo/ironruby-core -- Michael Letterle IronRuby MVP http://blog.prokrams.com
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
