Thomas Hafner wrote:
> The catch/throw solution seems uglier to me than the callcc solution.
> Do you have other suggestions?

Well, I don't really understand what's going on, but I observe from the 
catch/throw version that the generated symbol is in a local variable and 
doesn't appear to be passed downwards. So what's wrong with using the 
same symbol everywhere?

Or indeed, what's wrong with using loop { .... next ... } ?
-- 
Posted via http://www.ruby-forum.com/.