From: eregontp@... Date: 2015-11-23T14:40:33+00:00 Subject: [ruby-core:71641] [Ruby trunk - Bug #11718] Constant access on `nil` Issue #11718 has been updated by Benoit Daloze. I don't think it's intended, that commit should not introduce new behavior except on singleton class constants. @ko1: Could you confirm this is a bug? ---------------------------------------- Bug #11718: Constant access on `nil` https://bugs.ruby-lang.org/issues/11718#change-55043 * Author: Vais Salikhov * Status: Open * Priority: Normal * Assignee: * ruby -v: ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- It is possible to access top-level constants by doing `nil::CONSTANT`, which looks like a bug [according to Matz](https://github.com/opal/opal/issues/1197#issuecomment-158078778). Here are a couple of examples: ``` $ ruby -ve "Foo = 123; p nil::Foo" ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux] 123 ``` ``` $ ruby -ve "class A; Foo = 456; end; p nil::A::Foo" ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux] 456 ``` Thanks! -- https://bugs.ruby-lang.org/