From: "Hal E. Fulton" <hal9000@...>
Date: 2002-06-12T05:32:20+09:00
Subject: Re: ruby-dev summary 17252-17356

----- Original Message ----- 
From: "Yukihiro Matsumoto" <matz@ruby-lang.org>
To: "ruby-talk ML" <ruby-talk@ruby-lang.org>
Sent: Tuesday, June 11, 2002 11:18 AM
Subject: Re: ruby-dev summary 17252-17356


> Hi,
> 
> In message "Re: ruby-dev summary 17252-17356"
>     on 02/06/11, Dave Thomas <Dave@PragmaticProgrammer.com> writes:
> 
> |I'm not sure I understand why we'd want to change the '|...|' to
> |"<...>". If we don't need to use '<...>' for lexical reasons, wouldn't
> |it be better to use '|...|'? That way we'd leave the '<..>' option
> |free for use for some other purpose in future.
> 
> No, the idea was *not* changing, but providing both. '|...|' is for the
> current block parameters, which is processed by multiple assignment.
> And '<...>' is for function-like parameters, which is processed just
> like method arguments.

In that case, what does the semicolon
mean?

Hal Fulton