Facilitating the spread of knowledge and innovation in professional software development



Choose your language

InfoQ Homepage News ParseTree 3.0 Released, Many Related Libraries Updated

ParseTree 3.0 Released, Many Related Libraries Updated


Ryan Davis, who works on Rubinius for EngineYard, released a host of updates for ParseTree and related libraries.

ParseTree 3.0 (note: ParseTree 3.0.1 is now the latest version), comes with a few important changes:

* Split out sexp_processor project.
* ParseTree#process outputs a UnifiedRuby parse tree.
* Switched all ParseTree tests to RawParseTree tests.
* Added ParseTree tests.
* Added UnifiedRuby#process.

ParseTree's raw output is close to Ruby's internal parse tree; Unified Ruby is a cleaned up and simplified version of the normal output of ParseTree.

Sexp_Processor 3.0.0 is now available as a seperate Gem (it was formerly part of ParseTree). Sexp_processor allows to write and run visitors for analyzing ParseTree s-exprs.

Ruby2Ruby 1.2.0, a library that takes ParseTree s-exprs and turns them into Ruby source code, is available. All dependencies on ParseTree (the library) were removed, and the code was rewritten to use UnifiedRuby as input. Flog 1.2.0, a tool for analyzing code quality is now available.

Ruby_parser 2.0, also a project by Ryan Davis, is a Ruby parser written in Ruby. The new version includes a massive list of changes and bug fixes. Here just a few of the changes:

* Brought on the AWESOME! 4x faster! no known lexing/parsing bugs! [..]
* Added #store_comment and #comments [..]
* Added bin/ruby_parse [..]
* Added file and line numbers to all sexp nodes. Column/ranges to come. [..]


We need your feedback

How might we improve InfoQ for you

Thank you for being an InfoQ reader.

Each year, we seek feedback from our readers to help us improve InfoQ. Would you mind spending 2 minutes to share your feedback in our short survey? Your feedback will directly help us continually evolve how we support you.

Take the Survey

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.