tag:blogger.com,1999:blog-7638404154269297868.post1823704853211124735..comments2008-07-12T20:48:47.420-05:00drew olsonhttp://www.blogger.com/profile/05841768484212409868noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7638404154269297868.post-78139903311487625342008-07-12T19:32:00.000-05:002008-07-12T19:32:00.000-05:00Speaking of Ruby 1.9, I understand that parsing a block or proc into sexps (and from there to ruby in Ruby2Ruby) goes away in Ruby 1.9 as well.<BR/><BR/>On the other hand, Rubinius is working hard to support sexps being available at run time, so perhaps the syntactic abstraction progress will move away from MRI.Reginald Braithwaitehttp://www.blogger.com/profile/13132345822387028437noreply@blogger.comtag:blogger.com,1999:blog-7638404154269297868.post-40908416200583818162008-07-11T14:48:00.000-05:002008-07-11T14:48:00.000-05:00As you've noted, this unfortunately doesn't give you the full power to define new syntax constructs with new eval rules, but I guess it could be useful in a few cases.<BR/><BR/>Also, the example "with" macro takes advantage of a bug in Ruby 1.8 where block-local variables outlive the scope of the block, so this won't work in 1.9.Philhttp://www.blogger.com/profile/12517691336187602116noreply@blogger.com