On Wed, Oct 16, 2002 at 06:48:45AM +0900, TAKAHASHI Masayoshi wrote:
> Hi all,
> 
> Sorry to post so late. This is a summary of ruby-dev ML
> in these days.
> 
>   [ruby-dev:18465] warning for outer local variable assignment by block parameter
> 
> Tanaka Akira proposed warning for outer local variable assignment
> by block parameter. 
> 
> (ex.)
>   i = 0
>   foo.each{|i|  ## <= warning
>     .....
> 
> 
> GOTO Kentaro doubted if it is not the rare conditions, but Matz
> thinks that the frequency is not much for the risk, so it will
> be implemented.


If this is now considered "bad style", why was it allowed at
the beginning? I thought that the current semantics were the
result of a trade-off between expressive power/performance and
inability-to-shoot-yourself-in-the-foot.

matz's latest proposal clearly showed that he thought that assigning
to an external variable was justified in some occasions, and now he's
kinda saying that it should be avoided???

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

Those who don't understand Linux are doomed to reinvent it, poorly.
	-- unidentified source