From: "rits (First Last)" <redmine@...>
Date: 2013-11-06T07:22:23+09:00
Subject: [ruby-core:58182] [ruby-trunk - Bug #9083][Open]	BasicObject#method_missing does not always raise	NoMethodError for missing methods


Issue #9083 has been reported by rits (First Last).

----------------------------------------
Bug #9083: BasicObject#method_missing does not always raise NoMethodError for missing methods
https://bugs.ruby-lang.org/issues/9083

Author: rits (First Last)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [i686-linux]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN



  def method_missing(name, *)
    super
  rescue NoMethodError => e
    
  end

if the method is called without the receiver, it will raise just a NameError (variable or method missing)

the text of the error can differ depending on the presence of the receiver, but it seems counter-intuitive to not receive a NoMethodError when you are clearly attempting to call a non-existent method.  



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