From: "nobu (Nobuyoshi Nakada)" <nobu@...>
Date: 2013-01-04T13:02:04+09:00
Subject: [ruby-core:51234] [ruby-trunk - Bug #7564] r38175 introduces incompatibility


Issue #7564 has been updated by nobu (Nobuyoshi Nakada).


Anonymous wrote:
>  Before this changeset, `method_missing` *did* deal with all method
>  calls.

No, previously `respond_to?' was called so `method_missing' did *not* get called.

>  That's why this is not backwards compatible.

It depended on the internal behavior too much.
And the bug that overriding `method_missing' without `respond_to_missing?' has been revealed.
Just like overriding `hash' without `eql?'.

----------------------------------------
Bug #7564: r38175 introduces incompatibility
https://bugs.ruby-lang.org/issues/7564#change-35198

Author: tenderlovemaking (Aaron Patterson)
Status: Open
Priority: Normal
Assignee: mame (Yusuke Endoh)
Category: core
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2012-12-15 trunk 38381) [x86_64-darwin12.2.1]


r38175 introduces incompatibility with 1.9.3.  Before r38175, when looking for _dump, Marshal would not call method_missing.  Now marshal calls method_missing when trying to dump.

The following example exits with no error on 1.9.3, but on trunk it raises an exception (_dump() must return string (TypeError)):

class TR
  def initialize calls = []
    @calls = calls
  end

  def method_missing name, *args
    @calls << [name, args]
  end
end

Marshal.dump TR.new

I've attached a test case.


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