Re: concerns about Proc,lambda,block

On Thu, Mar 04, 2004 at 02:01:49PM +0900, Yukihiro Matsumoto wrote:
> |Based on what you said above, I'd expect the first and third calls of 
> |the following code not to generate a warning, but they do.
> 
> This warning is caused by Proc#call itself, not by lambda argument
> checker.  Its purpose is to warn and guide users to prepare future
> proc argument semantics, which |a| receives only one value.  The new
> semantics will be available on 2.0.

While you're fixing this, will you also be changing so
  some_method() { ... }
is the same as
  some_method() { || ... }
?

I found the present semantic ({ ... } being the same as
{ |*unused| ...}) very surprising when I discovered it,
and I still find it risky (it ends up with things failing silently if I
make an error in argument counts, rather than giving me an exception.)

Eivind.