From: Greg Weeks Date: 2007-11-16T19:01:39+09:00 Subject: Re: "&prock", not "&block" Eric Hodel wrote: > > It may be that "&foo" is pedagogically described as the "foo" > > parameter with an "&" modifier. But that is misleading. > > This is correct, and this is what happens. Its not misleading. I take your point. Thanks for the correction. Nevertheless, even though the argument is a block, the parameter foo is not. If you want to use the *block* argument in the method body, you use the expression &foo, not foo. foo is a proc; &foo -- an expression, not a parameter as I erroneously said -- is a block. > def z(&foo) > p foo > end > > z() # => nil Because no block was supplied. -- Posted via http://www.ruby-forum.com/.