Re: [ ruby-Bugs-7680 ] a block argument within a block which argument has the same name leaks

On Jan 8, 2007, at 3:56 PM, Yukihiro Matsumoto wrote:

> Hi,
>
> In message "Re: [ ruby-Bugs-7680 ] a block argument within a block  
> which argument has the same name leaks"
>     on Tue, 9 Jan 2007 08:38:25 +0900, Evan Webb  
> <[e-mail]> writes:
>
> |> It is a expected behavior during 1.8.  It will be fixed for 1.9.
> |
> |Really? What's the plan? I recall from rubyconf 2005 that block args
> |were going to get totally reworked, but I thought that the revision
> |planned had been thrown out in favor of leaving the current behavior.
>
> You can try it now via matzruby branch in the repository.
>
>   % cat test.rb
>   array = [1,2,3,4,5]
>   array.each {|allele|
>     puts allele
>     [10,10,10].map {|allele| allele}
>     puts allele
>   }
>   puts allele
>   % ruby -v test.rb
>   ruby 1.9.0 (2007-01-06 patchlevel 0) [i686-linux] - matz
>   /tmp/s.rb:7: warning: out-of-scope variable - allele
>   1
>   1
>   2
>   2
>   3
>   3
>   4
>   4
>   5
>   5
>   /tmp/s.rb:7: undefined local variable or method `allele' for  
> main:Object (NameError)

Hrm. So it warns about usage outside the block, but it doesn't allow  
it to be overridden? I'd think there should have been a warning on  
line 4 that the 'deeper' allele isn't the same as the shallower one.  
Also, this implies that all 'deeper' block variables can't be pulled  
out of the block, is that true? Or are their special rules applied to  
the block arguments?

  - Evan

> -- 
> 							matz.
>