Werner Schuster (murphee) wrote: > Charles Oliver Nutter wrote: >> - Decide on a standard AST structure to be built out of this? (for >> example, JRuby's AST is starting to differ from Ruby's, so even if we >> port ParseTree we'll have compatibility issues...so perhaps we >> > > Actually, I'm currently putting the finishing touches on a JRuby (pure > JRuby, no Java code) version of parsetree > (well, actually something that outputs the same nested lists as the > original parsetree; porting the C code of parsetree isn't possible). > > I'm currently trying to get parsetree 1.6s testsuite to complete (50 > failures to go) - and I believe there are some places where there are > some differences between JRuby/CRuby ... notably on the :dasgn/:lasgn > AST nodes. (Mind you: these might just be my own stupid errors). > > I can provide a preliminary version if someone wants to, but I'd rather > minimize the number of failures and provide some samples before going > public.
There are definitely going to be things that differ...more and more as we start making our own changes to the grammar and AST for performance and compilation. However it will still be very useful to have parsetree working in any form, since we'll be able to hook up similar tools. Feel free to polish it up as you like, but maybe it could live in the jruby-extras project (or a project of your own). -- Charles Oliver Nutter, JRuby Core Developer [EMAIL PROTECTED] -- [EMAIL PROTECTED] Blogging at headius.blogspot.com _______________________________________________ Rubygrammar-grammarians mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygrammar-grammarians
