Project

General

Profile

Bug #6078

The name of a module nested in an anonymous module depends on how it was created

Added by brixen (Brian Shirai) over 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Target version:
-
ruby -v:
ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-darwin10.8.0]
Backport:
[ruby-core:42865]

Description

If a module is nested under an anonymous module, the nested modules name will depend on how the module is created. See below:

$ irb
1.9.3p125 :001 > m = Module.new
=> #Module:0x000001009e1398
1.9.3p125 :002 > n = Module.new
=> #Module:0x000001009e1ca8
1.9.3p125 :003 > m::N = n
=> #Module:0x000001009e1ca8
1.9.3p125 :004 > m.name
=> nil
1.9.3p125 :005 > n.name
=> nil
1.9.3p125 :006 > m.constants
=> [:N]
1.9.3p125 :007 > module m::O
1.9.3p125 :008?> end
=> nil
1.9.3p125 :009 > m.constants
=> [:N, :O]
1.9.3p125 :010 > m::N.name
=> nil
1.9.3p125 :011 > m::O.name
=> "#Module:0x000001009e1398::O"
1.9.3p125 :012 > m.const_get(:N).name
=> nil
1.9.3p125 :013 > m.const_get(:O).name
=> "#Module:0x000001009e1398::O"
1.9.3p125 :014 > M = m
=> M
1.9.3p125 :015 > m::N.name
=> "M::N"
1.9.3p125 :016 > m::O.name
=> "#Module:0x000001009e1398::O"

Thanks,
Brian

Updated by brixen (Brian Shirai) over 8 years ago

There is a case not given above where it may make sense to give the class/module a name based on #inspect output of the containing class. This case is when the containing class is a singleton class:

$ irb
1.9.3p125 :001 > obj = Object.new
=> #Object:0x00000101147d30
1.9.3p125 :002 > class << obj
1.9.3p125 :003?> class B
1.9.3p125 :004?> end
1.9.3p125 :005?> end
=> nil
1.9.3p125 :006 > obj.singleton_class.name
=> nil
1.9.3p125 :007 > obj.singleton_class.const_get(:B).name
=> "#Class:0x00000101142948::B"
1.9.3p125 :008 >

However, note that the singleton class itself has no name, so giving the nested class/module a name like "#Class:0x00000101142948::B" seems wrong.

Thanks,
Brian

Updated by ko1 (Koichi Sasada) over 8 years ago

  • Assignee set to nobu (Nobuyoshi Nakada)
#3

Updated by shyouhei (Shyouhei Urabe) over 8 years ago

  • Status changed from Open to Assigned
#4

Updated by nobu (Nobuyoshi Nakada) almost 8 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

This issue was solved with changeset r36574.
Brian, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.


variable.c: tmp_classpath

  • variable.c: store anonymous class path in tmp_classpath but not in classpath. [ruby-core:42865][Bug #6078]

Updated by nobu (Nobuyoshi Nakada) almost 8 years ago

  • % Done changed from 100 to 50

Updated by nobu (Nobuyoshi Nakada) almost 8 years ago

  • % Done changed from 50 to 100

Also available in: Atom PDF