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

----- Original Message -----
From: "Kent Dahl" <kentda@stud.ntnu.no>
Newsgroups: comp.lang.ruby
To: "ruby-talk ML" <ruby-talk@ruby-lang.org>
Sent: Tuesday, June 11, 2002 4:00 PM
Subject: Re: ruby-dev summary 17252-17356


> "Hal E. Fulton" wrote:
> > From: "Yukihiro Matsumoto" <matz@ruby-lang.org>
> > > 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?
>
> The same, I would assume. Even if the parameter assignment is done like
> with functions, you wouldn't want the all variables to be local to the
> block only. Function-like doesn't mean a full-on stacklevel (I hope),
> but a move away from the sometimes very confusing parallell assignment
> rules that go into effect in blocks.
>
> .... if I understood the pervious posts correctly ...

I would bet a nickel (a yen?) this is not
what Matz has in mind.

I don't think that the parallel assignment rules
were what made this confusing, but the fact that
outside variables were used if they existed. Well,
that can be viewed as a consequence, I guess.

I doubt that we will see function-like non-local
pseudo-parameters in the future. But I could be
very wrong.  :)

Hal Fulton