Bug #2420: super call may use wrong receiver object

• Status: Closed
• Assignee: ko1 (Koichi Sasada)
• Target version: 2.0.0
• ruby -v: ruby 1.9.2dev (2009-12-01 trunk 25970) [i386-darwin9.0]

[nobu (Nobuyoshi Nakada)]

=begin
The code below prints:
C
main
Object::m

which means that the super calls the instance method B#m on a receiver that is not an instance of B. It's not what makes the super call to pick the main object as a receiver in this case. I would expect it to use the "self" object that the block captures, i.e. the class object C, and thus an exception "no superclass method `m' (NoMethodError)" should be raised.

class B
def m
p self
puts self.class.to_s + '::m'
end
end

class C < B
q = Proc.new do
p self
super()
end

mq = define_method :m, &q

mq.call
end

BTW: The behavior is even worse in Ruby 1.9:
ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-mswin32]
C
a.rb:11:in ==': wrong number of arguments(0 for 1) (ArgumentError) from a.rb:11:in block in class:C'
from a.rb:16:in call' from a.rb:16:in class:C'
from a.rb:8:in `'
=end

[mame (Yusuke Endoh)]

• Assignee changed from nobu (Nobuyoshi Nakada) to ko1 (Koichi Sasada)
• Target version set to 2.0.0

=begin
Hi,

I committed r28043 as temporary measure for 1.9.2 release.
This will be fixed correctly at 1.9.3 or later.
See [Bug #2502] [Bug #3136] in detail.

--
Yusuke Endoh [e-mail]
=end

[wanabe (_ wanabe)]

• Status changed from Open to Closed

=begin
This issue was solved with changeset r29063.
Yusuke, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

=end

[wanabe (_ wanabe)]

• Status changed from Closed to Open

=begin

=end

[shyouhei (Shyouhei Urabe)]

=begin
Hi, can I close this?
=end

[ko1 (Koichi Sasada)]

wanabe-san,

Should we keep it open or not?

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

This issue has gone away.