From: "David A. Black" <dblack@...>
Date: 2005-01-21T22:41:41+09:00
Subject: Re: Protected instance variables

Hi --

On Fri, 21 Jan 2005, Mystifier wrote:

> By going with C++ convention, currently @vars are protected, new ones will
> be private. Right?

I'm not sure whether it maps onto C++, but I don't think that's a
goal.  My understanding was that the problem was accidental
overwriting of instance variables -- for example, if you include a
module but haven't seen the code so you don't know what names the
author used for instance variables.  So having them be
[protected,private] (not sure which is the right term) would mean you
could make up your own instance variable names in class or module
scope and not have to worry.


David

-- 
David A. Black
dblack@wobblini.net