On Monday 17 January 2005 02:51 am, Martin DeMello wrote:
| David A. Black <dblack / wobblini.net> wrote:
| > You're right -- I meant to clarify that I'm talking about 2.0 class
| > vars, which as I understand it will be truly per-class and will differ
| > from instance variables of Class objects principally in that they will
| > be in scope in instance methods.  I would rather not have a separate
| > construct that overlaps so much with instance variables.
|
| I can think of at least one good us for the current @@ variables -
| subclassable GUI components that inherit hierarchy-shared look-and-feel
| properties from the parent class. What would be the elegant way to do
| this if @@ variables go per-class?

You would have to do it via class instance vars. The problem with these IMHO 
is still the intialization issue, as with modules (see ruby-talk:121611, 
http://urltron.com/nd) Matz, do you think we can get something in the way of 
remedying that? For me it's one of the biggest sores in my code.