From: ts <decoux@...>
Date: 2003-01-12T23:14:41+09:00
Subject: Re: Strange message when superclass expression raises an error

>>>>> "J" == Jeremy Henty <jeremy@chaos.org.uk> writes:

J> "superclass undefined"?  What happened to the real error?  If Ruby had
J> reported the original error properly it would have saved me a certain
J> amount of frustration.  Surely the error should simply propagate to
J> top level, just as when calling Class.new(foo) ?

 Well, this is changed in 1.8.0

pigeon% ruby -ve 'def foo ; raise "foo" end; class Foo < foo; end'
ruby 1.8.0 (2003-01-09) [i686-linux]
-e:1:in `foo': foo (RuntimeError)
        from -e:1
pigeon% 


Guy Decoux