Bug #4502: strange Module.new behaviour

• Status: Closed
• Assignee: nobu (Nobuyoshi Nakada)
• Target version: 2.0.0
• ruby -v: ruby 1.9.1p430 (2010-08-16 revision 28998) [i386-mingw32]

[evilbrain (Andy Bogdanov)]

=begin
First I create a proc:
p = proc {
self::X = Class.new
def self.X
X.new
end
}
Then I create a module:
A = Module.new(&p)
puts A.X # => #<A::X:0x9c2e774>
Then I create another module:
B = Module.new(&p)
puts B.X # => #<B::X:0x9c39304>
Everything seems to be ok. But after module B was created (({A.X})) started to return instances of (({B::X}))
puts A.X # => #<B::X:0x9c38238>

When (({self::X.new})) is used instead of (({X.new})) everything works as expected.

More info can be found here http://www.ruby-forum.com/topic/1275717
=end

[shyouhei (Shyouhei Urabe)]

• Status changed from Open to Assigned
• Assignee set to ko1 (Koichi Sasada)

=begin

=end

[ko1 (Koichi Sasada)]

• Target version set to 2.0.0

This issue have complex problems. I'll fix it 1.9.4 or later.

[ko1 (Koichi Sasada)]

• Assignee changed from ko1 (Koichi Sasada) to nobu (Nobuyoshi Nakada)

nobu, could you check it?
I think you tried something like this issue.

[nobu (Nobuyoshi Nakada)]

With latest version, A.X occurs NameError instead of returning B::X.

[nobu (Nobuyoshi Nakada)]

• Status changed from Assigned to Closed