Bug #6097: Weird constant behavior during inheritance...

• Status: Rejected
• Assignee: -
• Target version: -
• ruby -v: 1.9.3

[ddebernardy (Denis de Bernardy)]

class Parent
class Child
def foo
end
end
end
=> nil
class Test < Parent
end
=> nil
Test.const_defined?(:Child)
=> true
class Test
class Child
def bar
end
end
end
=> nil
Test::Child.new.respond_to?(:bar)
=> true
Parent::Child.new.respond_to?(:bar)
=> false # true expected...

Obviously, testing the object_id shows that Parent::Child and Test::Child are not the same class, but is this to be expected?

[fxn (Xavier Noria)]

Once Test::Child gets defined, both Parent and Test have Child among their very constants (and they are different classes). The ancestry chain is not even checked.

[matz (Yukihiro Matsumoto)]

• Status changed from Open to Rejected

Learn Ruby-way, please.