[ruby-talk:4703] Re: Two observations

Mark Slagell <[e-mail]> writes:

> (2) Which leads to the second observation: ver. 1.6 bails out on some errors
> that in 1.4.6 would be caught by a rescue clause.  This isn't necessarily a
> bad thing (at first glance it seems to honor a distinction between what in a
> compiled language would be compile-time and run-time errors), but might it be
> possible to optionally evoke the old behavior?

It still raises the exception, it's just that the hierarchy changed
somewhat, so that ScriptError is now longer a subclass of
StandardError.

  begin
    eval "grumpy old code"
  rescue
    puts "not here"
  rescue ScriptError => e
    puts "but here: #{e}"
  end

=>

  but here: (eval):1: undefined local variable or method `code' for #<Object:0x40197d30>


Regards


Dave