From: Yukihiro Matsumoto <matz@...>
Date: 2009-10-16T20:02:38+09:00
Subject: [ruby-core:26122] Re: [Bug #2206] lib/delegate: inconsistency between respond_to? and send

Hi,

In message "Re: [ruby-core:26080] [Bug #2206] lib/delegate: inconsistency between respond_to? and send"
    on Wed, 14 Oct 2009 13:06:09 +0900, Marc-Andre Lafortune <redmine@ruby-lang.org> writes:

|require 'delegate'
|class A
|  private
|    def private_method
|      :bar
|    end
|end
|
|x = SimpleDelegator.new(A.new)
|x.respond_to?(:private_method, true)  # ==> true
|x.send(:private_method)  # ==> NoMethodError

|I expected the call to private_method to be delegated. The attached patch fixes the problem. It is not very elegant but I couldn't think of anything better.

No, delegators should only delegate public methods.  I will make
#respond_to? to warn if you specify true for its optional argument.

							matz.