On Dec 5, 2003, at 10:31 AM, Weirich, James wrote:

> From: David A. Black [mailto:dblack / wobblini.net]
>
>> Oh, not that it matters but I got that wrong.  Tied for *first*
>> with doing nothing.  @_ way down at third :-)
>
> I tend to agree with this.  Having both protected and private instance
> variables is overkill and complicates the language.  If private 
> instance
> variables are prefered, then make them all that way.  It will break
> portability, but we expect some of that in moving to Ruby 2.
>
> Besides, leading underscores are /ugly/.  Leading underscores prefixed 
> by @
> are /very ugly/.
>
> So, here's my vote to *not* have two different kinds of instance 
> variables.

Me too. It's hard to sell Ruby to others in an organization where 
Python is the easy and safe choice. Adding "@_" would definitely be an 
argument against Ruby in that context.

Chris