On Fri, Nov 08, 2002 at 03:14:36AM +0900, Yukihiro Matsumoto wrote:
> Hi,
> 
> In message "Making Instace Variables Private/Local"
>     on 02/11/07, William Djaja Tjokroaminata <billtj / y.glue.umd.edu> writes:
> 
> |If you are still considering to use '@_var' or '@__var' to create class
> |private/local variables, are you open to the idea of simply making all
> |instance variables private?  The descendant classes then can access the
> |instance variables using 'self.var', where the method 'var' can either be
> |public or protected.
> 
> I am not brave enough to introduce such incompatibility.  I guess more
> than 60% of Ruby programs will not run after such change.

Were Ruby to be invented again, would you do it?

Put another way: do you think it is The Right Thing?

IMHO it is closer to it than what we have now.


PS: first post!

from my new PC in my new dorm, I mean :-)
-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

On a normal ascii line, the only safe condition to detect is a 'BREAK'
- everything else having been assigned functions by Gnu EMACS.
	-- Tarl Neustaedter