From: "MasterLambaster (Alex N)" <masterlambaster@...>
Date: 2012-08-15T21:00:48+09:00
Subject: [ruby-core:47211] [ruby-trunk - Feature #6828] Constancy of Constants


Issue #6828 has been updated by MasterLambaster (Alex N).


=begin
I think it might be implemented but i'd rather not do that.
The reason why its not equivalent is because the first statement means:
((|Define module Baz under Foo::Bar|))
The second one means:
((|Define module Foo, define module Bar under Foo, define module Baz under Foo::Bar|))

So it's not an issue in a common sense. In first case you try to create module under namespace that does not exist, that leads to error, and I think that is should be so. In the second case you you explicitly define all module structure.

=end

----------------------------------------
Feature #6828: Constancy of Constants
https://bugs.ruby-lang.org/issues/6828#change-28891

Author: trans (Thomas Sawyer)
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: 2.0.0


=begin
Could have swore there was a recent issue addressing this, but couldn't find it, so...

I hope by Ruby 2.0

  module Foo::Bar::Baz

will be equivalent to

  module Foo; module Bar; module Baz

That constant lookup doesn't work the same for both is really really really annoying.
=end



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