Hi --

On Thu, 5 Jul 2007, Gregory Brown wrote:

> On 7/4/07, dblack / wobblini.net <dblack / wobblini.net> wrote:
>
>> > I'm in favor of the new behaviour, but am not sure about the warning.
>> > My feeling is that any time I've used something like
>> >
>> > a = 1
>> >
>> > foo { |a| }
>> >
>> > It was a typo and I'd like to know about it.
>> 
>> It still sort of goes in a circle, though.  If the main goal is not to
>> use the same-named variable in both scopes, then what difference does
>> it make which behavior happens when you do it?
>
> Well by saying that (and I think you're right), aren't you arguing in
> favor of a warning? :)

My preference would be for it to stay as it now is (assignment
semantics), without a warning.  I've never been convinced that it's
such a big problem, and I think it's a pity to do away with the
assignment semantics which could prove useful.


David

-- 
* Books:
   RAILS ROUTING (new! http://www.awprofessional.com/title/0321509242)
   RUBY FOR RAILS (http://www.manning.com/black)
* Ruby/Rails training
     & consulting:  Ruby Power and Light, LLC (http://www.rubypal.com)