Hi --

On Sat, 14 Feb 2004, Joel VanderWerf wrote:

> David A. Black wrote:
> > Class variables, at least through 1.8.x, are essentially per-hierarchy
> > and not per-Class-object.  For 1.9/2.0, though, Matz has presented the
> > following new rules:
> > 
> >   * class variables will be local to the class/module
> >   * if you need to access class variables from outside,
> >     define accessors
> 
> The per-hierarchy thing was never very clear. Just _which_ hierarchy a 
> variable belongs to depends on the order in which it is first assigned:

See ruby-talk 19972 (and surrounding thread); I brought this up, and
Matz said, "I know this happens.  I consider this as an error that
Ruby does not detect yet."  The funny thing is... I could have sworn that
it was fixed somewhere > 1.6, but it still seems to happen at least as
recently as 1.8.0.  (Yes, I'm being lazy about testing the CVS :-)

It will become moot, though, after the new rules are implemented.


David

-- 
David A. Black
dblack / wobblini.net