On Sep 3, 2010, at 13:42 , Alex Chaffee wrote:

> So how do we do it? Doesn't Ruby have poor support for AST
> introspection (see
> http://blog.zenspider.com/2009/04/parsetree-eol.html)? Well, yes, it
> does, so we cheat: we figure out what file and line the assert block
> is defined in, then open the file, read the code, and parse it
> directly using Ryan Davis' amazing RubyParser and Ruby2Ruby. You can
> bask in the kludge by examining `chunk.rb` and `assert.rb`. If you
> find some code it can't parse, please send it our way.

HAHAHA!... you SICK SICK BASTARDS.... HAHAHAHA!

good work!

> Please feel free to challenge any of the above claims in a reply :-).
> I'd love to know if Ryan and the rest of the ruby-talk gang think this
> is an acceptable or an outrageous use of a parsing library. In any
> event, I think it constitutes a pretty compelling use case for adding
> Proc#to_sexp or equivalent to the MRI runtime.

Are you kidding? that output is freakin' beautiful!