Re: concerns about Proc,lambda,block

Hi,

In message "Re: concerns about Proc,lambda,block"
    on 04/03/05, Hugh Sasse Staff Elec Eng <[e-mail]> writes:

|Because it affects how return and errors are handled. The method
|that does something with this may be able to decide (based on what it
|has received) how to deal with failures, it may wrap the proc in a
|Thread.new(...){...}.value or something.  Also it improves clarity
|of code in the same way that block_given? does.  I can't really
|think of an example, but I think that is more my lack of imagination
|than anything else.

The difference still lies in the Proc code body, which you can't read
nor modify any way from Ruby code.  My opinion:

  * I still don't see the need to distinguish lambda wrapped procs and
    normal procs.

  * if someone come up with the good reason, I'm happy to separate
    these two, not by providing wrapped? (or lambda?) method, but by
    separating classes (Proc and Lambda, perhaps).

							matz.