From: "alexeymuranov (Alexey Muranov)" <redmine@...>
Date: 2013-03-30T18:41:19+09:00
Subject: [ruby-core:53841] [ruby-trunk - Bug #8189][Open] (one more) inconsistency between Class and Module as namespaces


Issue #8189 has been reported by alexeymuranov (Alexey Muranov).

----------------------------------------
Bug #8189: (one more) inconsistency between Class and Module as namespaces
https://bugs.ruby-lang.org/issues/8189

Author: alexeymuranov (Alexey Muranov)
Status: Open
Priority: Low
Assignee: 
Category: core
Target version: 
ruby -v: 2.0.0


=begin
(I will only mention in parentheses that inheriting (({Class})) from (({Module})) looks like a bad idea to me, i would have preferred that both inherited from some (({Namespace})) class.)

While trying to answer ((<this SO question|URL:http://stackoverflow.com/questions/6254496/is-it-possible-to-give-a-sub-module-the-same-name-as-a-top-level-class/15716986#15716986>)), i have noticed the following inconsistent behavior between classes and modules used as namespaces:

  A = 0

  class C; end
  module M; end

  C::A # warning: toplevel constant A referenced by C::A
  M::A # uninitialized constant M::A (NameError)
=end



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