ts <decoux / moulon.inra.fr> writes:

> >>>>> "G" == GOTO Kentaro <gotoken / math.sci.hokudai.ac.jp> writes:
> 
> G> For example, loop{|a| ... } means as same as the current model.  In
> G> loop{|a;b| b = a; .... }, b is a shadowed counter.
> 
>  Perhaps you can write  loop{(a;b) .... } where a and b are new local
> variables in the current scope

Doesn't that break existing code, though?

   n = 99
   b = a.collect {(n)}


I'm wondering: was the idea of having a different block type for scope 
protection just too stupid? I've seen no comments about
ruby-talk:12393.

Dave