Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!olivea!apple!bionet!arisia!roo!gregor
From: gregor@parc.xerox.com (Gregor Kiczales)
Newsgroups: comp.lang.objective-c
Subject: Re: Requirements for Class Variables for Objective-C
Message-ID: <GREGOR.90Oct14231438@spade.parc.xerox.com>
Date: 15 Oct 90 06:14:38 GMT
References: <5638@stpstn.UUCP> <270A66D0.14263@ics.uci.edu>
	<kenneth.655324438@exklusiv>
Sender: news@parc.xerox.com
Organization: Xerox Palo Alto Research Center
Lines: 13
In-reply-to: kenneth@EB.se's message of 7 Oct 90 18:33:58 GMT


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

In CLOS, we did 2.  It seemed natural, and it works well.  But, there
are plenty of cases where what users want is 1.  Fortunately, in CLOS,
the Metaobject Protocol makes it easy for users to add this kind of
class variable themeselves.  But, given that you don't have a Metaobject
Protocol, I would say do both 1 and 2.