I have too much faith in core classes being specified correctly sometimes...I'll learn someday.On 4/6/06, Nick Sieger <
[EMAIL PROTECTED]> wrote:On 4/6/06,
Charles O Nutter <[EMAIL PROTECTED]> wrote:
How's this for weird: we didn't have NameError rooted correctly.Yep, I just came to the same conc
On 4/6/06, Charles O Nutter <[EMAIL PROTECTED]> wrote:
How's this for weird: we didn't have NameError rooted correctly.Yep, I just came to the same conclusion and was about to submit a patch -- you beat me to it. Fixing the superclass for NameError fixed the example script in my first message in t
How's this for weird: we didn't have NameError rooted correctly.In JRuby 0.8.2, 0.8.3, and HEAD we had NameError as a subclass of ScriptError, instead of StandardError. As it turns out (and I had to study a bit for this) a bare rescue automatically rescues only StandardError descendents. Since we h
On 4/5/06, Charles O Nutter <[EMAIL PROTECTED]> wrote:
My money is on a parser change.
It seems to parse ok, but it's as if the logic executed by the generated AST is not behaving the same way as C Ruby. Do you think the parser is mis-interpreting the _expression_ following "rescue" as some sort o
That's an interesting one; if it's not supported now it may require a parser change to wrap the specified code in an implicit begin block. You could look into how RescueNode is handled, but it's pretty deep stuff.My money is on a parser change.
On 4/5/06, Nick Sieger <[EMAIL PROTECTED]> wrote:
Some
Some Rails code uses a shorthand rescue syntax that JRuby does not seem to appreciate. Witness the following tidbit:def dummy(obj) obj.missing_method rescue "missing_method"endputs dummy("hello")
In C Ruby:[20:57:24][~/Projects/jruby]$ ruby test/testRescue.rb missing_methodIn JRuby:[20:57:30][~/P
