From: Daniel Nugent <nugend@...>
Date: 2006-02-13T03:55:47+09:00
Subject: Re: Rescuing blocks?

Whoops, shoulda thought of that, a-doy.
Okay, it's pretty simple, here's what I'd like to do (you canextrapolate the rest of the syntax from the simple example):
foo = [1, 2, 3]
foo.each do |o|  raise "Oh noes, it's number 2!" if o == 2rescue Exception => e  puts e.to_send
And so on and so forth.  It seems pretty natural to me.... I don'tthink it breaks anything (least not off the top of my head)...
On 2/12/06, David Vallner <david@vallner.net> wrote:> D�a Nede�a 12 Febru�r 2006 19:26 Daniel Nugent nap�sal:> > Hey guys,> >> > I was working on a DSL for some asynchronous programming stuff and I> > realized it'd be really nice if a block could rescue an exception.> >> > So I went into IRB to see if it works and got a parse error.  I> > suppose you need a begin... end block or a proper method to have a> > rescue block right now.> >> > I was wondering if there's any reason why this is so?  It'd seem> > pretty natural to me that a block could have rescue/else/ensure> > conditions since a method body can have them.> >> > Has this been discussed elsewhere?> >> > Thanks,> >> > --> > -Dan Nugent>> I'm afraid I don't quite catch your drift. What do you mean by a block not> rescuing an exception? Some example code wouldn't hurt.>> David Vallner>>

---Dan Nugent