From: matz@... (Yukihiro Matsumoto)
Date: 2003-08-13T23:10:23+09:00
Subject: Re: Nested class/module namespace

Hi,

In message "Re: Nested class/module namespace"
    on 03/08/13, "Nathaniel Talbott" <nathaniel@NOSPAMtalbott.ws> writes:

|> This would be the same as doing:
|> 
|>   module M; end
|>   c = Class.new
|>   M::C = c
|>   p M::C
|
|OK, I understand how it's behaving... but why? What's the benefit of it
|behaving like that? What's the downside of it behaving as nested classes do
|now?

Because it's not nested at all.  It is confusing for me, if it behaves
like nesting.  Nested constant scope was introduced only for one
purpose.

  module M
    class C
       C.foo     # want to access C here.
    end
  end

In the cases like

  class M::C
  end

you don't need dereferencing like above.

							matz.