チケット #2080 が更新されました。 (by Etienne Vallette d'Osia)


An other way would be to create a spec to represent ruby code into s-expression.
Each interpreter transforms its internal representation into a standard s-expression, 
so ruby gains a cool and powerful lisp feature.
Maybe a simple lib/gem could provide this feature to some of the existing interpretors (like ruby_parser for cruby 1.8).

It makes the file-pointing impossible (unless a temp file is created, containing only s-expressions)
but if it is possible to transform iseq to sexpr, it will makes the files-pointing useless.

Building source from sexpr is already done by some projects, so I suppose it's not a big deal.
----------------------------------------
http://redmine.ruby-lang.org/issues/show/2080

----------------------------------------
http://redmine.ruby-lang.org