Making sense out of ruby's dynamic method calls

Case 1:

def n
puts "inside n"
end

def m(&m2)
m2.call
end

m(&method(:n))
m() {puts "hello"}

>> inside n
>> hello


Case 2:

def m()
yield
end
m(&method(:n))
m() {puts "hello"}

>> inside n
>> hello

Case 3:

def m(&m2)
m2.call
yield
p m2.class
end

m(&method(:n))
m() {puts "hello"}

>> inside n
>> inside n
>> Proc
>> hello
>> hello
>> Proc


Case 4: (Adding checking before calling)

def m(&m2)
m2.call unless m2.nil?
end

def m
yield if block_given?
end

Case 5:

p = Proc.new(&method(:n))
p.call
m(&p)

>> inside n #p.call
>> inside n #m(&p)

Case 6:
p = Proc.new() {puts 'hello'}
p.call
m(&p)

>> hello #p.call
>> hello #m(&p)

Case 7:

p = method(:n).to_proc
m(&p)

>> inside n


Conclusions and Summary
- The decision of using yield or call in a method does not affect how the method is invoked. It can be given a block or a &Proc, or a &Method.
- If yield is used, then block_given? is used for checking.
- If call is used, then nil? is used for checking.
- For a method m, a parameter of the form &m2 can only appear at the end of the parameter list (therefore, at most once). This parameter corresponds to a block, or a &Proc, or a &Method.
- A method symbol (or a function pointer) can be created using "method(:)" (note the usage of ':' to obtain a symbol).
- A procedure can be created using "Proc.new(&x)" where x is a Method or a Proc. A procedure can also be created using Proc.new() {...} via a block.

Comments

capsid said…
Great post! I had trouble figuring out what ruby's ampersand was for until I read this.

Many thanks.
December 7, 2008 at 10:04 AM
Post a Comment

Popular posts from this blog

Creating an HTTP Streaming Client in Silverlight

I read and played with WebClient and HttpWebRequest classes. Both of these classes allow you to make requests to an http server. Once you make the request, you give a callback that is invoked once the response is received so you can happily examine the response. Let's say your HTTP server is streaming a file, or it wants to hold on to your request and sends messages as necessary from the same connection. To be able to work with such a server, your http client must be able to read the data as soon as it is available without requiring the response to be received completely.  After searching silverlight forums I found a solution. The solution assumes that you have a control on the server code or the response you are getting is bigger than 4KB (IE buffers upto 4KB). Here is the code snipped for your client side: HttpWebRequest request = (HttpWebRequest)WebRequest.Create(uri); request.Method = "POST"; request.AllowReadStreamBuffering = false; try {  request.BeginGetResponse(On...
Read more

The Order of Rails Validation Filters

Here are the available Rails validation filters: before_validation_on_update before_validation_on_create validate validate_on_update validate_on_create after_validation after_validation_on_update after_validation_on_create before_save before_update before_create after_update after_create after_save These filters are callbacks that are invoked automatically. The difference between update and create is really with respect to the database. If the record you are saving is a new record in the db, then it means you are creating. If the item already exists but you are making a change, then it means you are updating. In other words, it does not matter, whether you called obj.save or obj.create, before_update filter will be invoked. The same is true for obj.save vs. obj.update_attributes. So no matter what Active record method you invoke the filter is decided based on the database record. How about before_save, before_after_save? They will always be invoked whether you are creating or updating....
Read more

Comparison of equality operators in Ruby: == vs. equal? vs. eql? vs. ===

Here is a short explanation of when these predicates are true (From http://www.wellho.net/mouth/985_Equality-in-Ruby-eql-and-equal-.html) The == comparison checks whether two values are equal eql? checks if two values are equal and of the same type equal? checks if two things are one and the same object. How do I remember which is which ... The longer the operator, the more restrictive the test it performs Let's understand the differences with some examples. Each "abc" below is a different object. Therefore, equal? is false. irb(main):065:0> "abc".object_id => 24173330 irb(main):066:0> "abc".object_id => 24165760 irb(main):067:0> "abc" == "abc" => true irb(main):068:0> "abc".eql? "abc" => true irb(main):069:0> "abc".equal? "abc" => false As you might expect, there is a single instance of 1. Therefore, all comparisons are true. irb(main):094:0> 1.class =>...
Read more