Eric Hodel wrote:
> Class doesn't matter, methods do.

You're preaching to the choir :-)

> I'm (almost) always passing in a block, so its a block.

If you're passing in a block, then the method parameter is something
like "&foo".  If you're passing in a proc, then the message parameter is
something like "foo".  In either case, in the method body, "&foo" is a
block, and "foo" is a proc.

It may be that "&foo" is pedagogically described as the "foo" parameter
with an "&" modifier.  But that is misleading.  The block argument is
bound to "&foo", not to "foo".  And the block argument is accessible in
the method body -- as "&foo".

So in all cases, "&foo" is a block iff "foo" is a proc.
-- 
Posted via http://www.ruby-forum.com/.