[ruby-core:26437] [Bug #1151] Aliased methods change super logic when retrieved with Object#method

Issue #1151 has been updated by Matt Jones.


Not sure if this is related or not, but I've run across another very similar issue regarding method(:name).call not being equivalent to calling the method.

Example is here: http://gist.github.com/221585

The net result is more dramatic than in this example; rather than simply calling the wrong method, the call to super fails with 'superclass not found'. But the essential problem is the same - calling B.new.foo produces a different result than B.new.method(:foo).call.

@Charles - can you try the Gist out on JRuby? Thanks!
----------------------------------------
http://redmine.ruby-lang.org/issues/show/1151

----------------------------------------
http://redmine.ruby-lang.org