Re: Nesting and constants

On Tue, Aug 7, 2012 at 6:06 PM, Thomas Thomassen <[e-mail]>wrote:

The comments there reflects what Matz mentions here:
>
>
> http://www.justskins.com/forums/nested-class-module-namespace-42955.html#post129248
>
> But I still don't understand why this is considered expected behaviour.
>

Well, it is expected behavior because that's the way Ruby works.

A given module can be stored in a hundred constants in dozens of
differently nested constant paths. Constants are largely irrelevant to
Ruby, Ruby semantics are defined around module and class objects.

So, the rule is that whatever module object is opened by the module
keyword, that's what gets pushed to the nesting. It is simple, and it works
in all cases. It does not matter the constant path used to reach the module
object. Given (untested code):

    module M
      N = Module.new
    end

    module A
      module B
        C = M::N
      end
    end

    module M::N
      # (1)
    end

    module A::B::C
      # (2)
    end

    X = M::N
    module X
      # (3)
    end

the nesting in (1), (2), and (3) is the same (M::N). The fact that we got
the M::N module via X or A::B::C is irrelevant. And the fact that we reach
it via M::N is equally irrelevant by the same principle. *Constants do not
matter*, Ruby only cares about the module objects they yield.

In my view all is round and follows those basic axioms, but of course the
only one who can ensure which is the rationale is Matz himself.