Charles Oliver Nutter wrote: > Subject basically says it all. It would probably need to be down to zero > failures, but I'm all for just including JParsetree in core. It seems > like it's become the de-facto standard for writing macro-like utilities > in Ruby, and having it in core would open the door to running Rubinius's > compiler directly (not to mention Ruby2Ruby and friends). > Coolio!
I just updated jparsetree in SVN to work with JRuby 0.9.9. I also added the capability to add source locations to the individual nodes, details here http://jroller.com/page/murphee?entry=jparsetree_now_with_source_locations This will allow to use jparsetree for static analysis tools (or generally, tools that look at Ruby source code), since these need proper source range information. About the failures: - the current SVN trunk version is down to 6 failures and one error; - I hope I can get someone from the core team to give me a hand with some of the failures for runtime features, ie. ParseTree allows to get the AST of methods at runtime; the problem: the test suite has some nasty cases dynamically added method (with define_method at various stages of class loading, also attr_accessor). I managed to handle 2-3 of them, but there are 1-2 others that I can't figure out. I can send details (for impatient folks: the test suite has a class Examples which contains these). murphee _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
