On Fri, Dec 14, 2001 at 02:17:13AM +0900, ts wrote:
>  When you write
> 
>  Proc.new {|a| }
> 
>  |a| is seen by ruby as multi-assignement, and it use the same rules. Rule
>  that you have broken because you don't see it as a multi-assignement.

But these same rules do not apply to methods that have been turned into
procs:
  class Foo
    def foo(x)
    end
  end
  
  f = Foo.new
  p = f.method(:foo).to_proc
  p.call(1, 2, 3)

since this generates an exception.  It seems to me that a proc should be
treated as an anonymous function.  Is there any useful reason for
treating it otherwise?

Paul