14

I would like to know if I could force this to happen

class A
  def bomb ; "bomb" ; end
end

class B ; end

bomb = A.instance_method(:bomb)

b = B.new
bomb.bind(b)

currently it throws the error TypeError: bind argument must be an instance of A

I find this very limiting concerning what I can do with these unbound methods, the possibilities are a bit limiting. In cases like these (and I'm not referring only to idempotent functions) it would make sense right? And an execution error would have sufficed, In case I would be handling variables from A which are not replicated in B. I'd really like to know how to force this bind.

Tobias Kienzler
  • 25,759
  • 22
  • 127
  • 221
ChuckE
  • 5,610
  • 4
  • 31
  • 59
  • Something interesting that is possible: `Object.instance_method(:to_s).bind("hello world").call #=> "#"`. I don't think it's possible to force the binding in your example though. – Scott Olson Nov 05 '12 at 14:57
  • 2
    Yes, that is because String inherits from Object, and you can bind superclass instance methods to its children class instances. An example: class A ; def t ; "A" ; end ; end ; class B < A ; def t ; "B" ; end ; end ; A.instance_method(:t).bind(B.new).call . But still, I would like to make the method a function and then a proc and then call it wherever I wanted. But maybe I'm a dreamer :) – ChuckE Nov 05 '12 at 16:31
  • if `A` would have been a `module`, then it is possible in ruby 2 – Amol Pujari Dec 12 '13 at 10:33

2 Answers2

2

You cant bind instance of a class with the method of another class. Unless instance is an object of this class, or its sub-classes.

And this is obvious too, the detail of one class cant be transferred to instance of other class. It can be bound with only that instance which is authorized to carry that information that is, the instance of that class or its sub-class.

Hence ruby also maintains encapsulation by not binding method of particular class to instance of another class.

Akshay Vishnoi
  • 1,252
  • 12
  • 15
2

Method and UnboundMethod types expect that the bind target must be subclass of the original class where you have referenced the method. Converting the method to proc gets rid of the subclass constraint, but only Method has to_proc method implemented.

class A
  def bomb ; "bomb" ; end
end

class B ; end

bomb = A.new.method(:bomb)

B.send(:define_method, :bomb_in_b, &bomb) #converting to proc

b = B.new
puts b.bomb_in_b

Tested in Ruby 2.2.3

karatedog
  • 2,508
  • 19
  • 29