From: Yukihiro Matsumoto <matz@...>
Date: 2011-07-22T02:40:38+09:00
Subject: [ruby-core:38353] [Ruby 1.9 - Bug #5067] BasicObject's constant lookup documentation


Issue #5067 has been updated by Yukihiro Matsumoto.


Well, BasicObject is a blank slate, and adding const_missing to it could affect all classes in the Ruby class hierarchy.  Even though it might solve your problem, that could have huge side effect, e.g. entering infinite loop.

OKay, as a compromise, I can accept more clarified version of workaround.


  class Foo < BasicObject
    def self.const_missing(name)
      ::Object.const_get(name)
    end
  end

How do you think?

matz.
----------------------------------------
Bug #5067: BasicObject's constant lookup documentation
http://redmine.ruby-lang.org/issues/5067

Author: Shyouhei Urabe
Status: Open
Priority: Normal
Assignee: 
Category: DOC
Target version: 
ruby -v: doesn't matter


Take a look at https://github.com/ruby/ruby/pull/31 .

It's OK for me to merge this request -- no technical difficulties -- but is it a right thing to be documented?


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