Actions
Bug #9083
closedBasicObject#method_missing does not always raise NoMethodError for missing methods
Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
ruby 2.0.0p247 (2013-06-27 revision 41674) [i686-linux]
Backport:
Description
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.
Actions
Like0
Like0