From: Nathaniel Talbott <nathaniel@...>
Date: 2003-08-13T23:26:44+09:00
Subject: Re: Nested class/module namespace

Yukihiro Matsumoto [mailto:matz@ruby-lang.org] wrote:

> 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

Oops... I guess I've been using it incorrectly :-). So it's not for this
reason?

  module M
    class C
      M::FOO       # want to access M here.
    end
  end

> In the cases like
> 
>   class M::C
>   end
> 
> you don't need dereferencing like above.

Well, this seems a little confusing to me:

  class M::C
    def C.m
    end
  end

  => NameError: uninitialized constant M::C::C

If it had nested scope, this wouldn't happen, right?


Nathaniel

<:((><