From: "Jesús Gabriel y Galán" <jgabrielygalan@...>
Date: 2012-05-19T15:37:39+09:00
Subject: Re: Methods as arguments?

On Sat, May 19, 2012 at 6:05 AM, Matthew Kerwin <matthew@kerwin.net.au> wrote:
> Just to make sure my head's on straight, the method is still bound to
> its original object, right?  Any @instancevars in there will still
> refer to the right instance?

Yes, check this:

1.9.2p290 :001 > class A
1.9.2p290 :002?>   def initialize
1.9.2p290 :003?>     @a = 3
1.9.2p290 :004?>     end
1.9.2p290 :007?>   def m
1.9.2p290 :008?>     puts @a
1.9.2p290 :009?>     end
1.9.2p290 :010?>   def get_me_the_method
1.9.2p290 :011?>     method(:m)
1.9.2p290 :012?>     end
1.9.2p290 :013?>   end
 => nil
1.9.2p290 :014 > the_method = A.new.get_me_the_method
 => #<Method: A#m>
1.9.2p290 :015 > the_method.call
3
 => nil

You can also have Unbound methods:
http://www.ruby-doc.org/core-1.9.3/UnboundMethod.html
but you have to bind them to some instance before calling them.

Jesus.