Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!apple!portal!sv!moose
From: moose@svc.portal.com
Newsgroups: comp.lang.objective-c
Subject: Re: Requirements for Class Variables for Objective-C
Message-ID: <1990Oct15.185718.8342@svc.portal.com>
Date: 15 Oct 90 18:57:18 GMT
References: <5638@stpstn.UUCP> <270A66D0.14263@ics.uci.edu> <kenneth.655324438@exklusiv> <GREGOR.90Oct14231438@spade.parc.xerox.com>
Organization: Software Venture
Lines: 18

In article <GREGOR.90Oct14231438@spade.parc.xerox.com> gregor@parc.xerox.com (Gregor Kiczales) writes:
>
>With regard to the question about what kind of class variables people
>want, here is a comment from another community.
>
>> 1 -- each subclass has its own copy of its parent's class variables
>> 
>> 2 -- all subclasses share a single copy of their parent's class variables

I think this arguement is beginning to get silly.  If you do #2, you can 
always do #1 by adding a new variable and overridding all methods that affect
the variable in question.  If you do #1, there is no way to do #2.  
Therefore, #2 should be done.
-- 
Michael Rutman				|	moose@svc.portal.com
Cubist					|	makes me a NeXT programmer
Software Ventures			|	That's in Berkeley
smile, you're on standard disclaimer	|	<fill in with cute saying>