I agree with Greg. Class variables would/should participate fully in the objC inheritance mechanisms. This would be a natural extension to the language since it already has Class methods (and also encourages the use of properties). From a modelling point of view the distinction between a method and a instance variable is somewhat arbitrary to the clients of the class. It can be a store vs compute decision: i.e., an implementation detail.
Martin On 2011-08-03, at 2:21 AM, Greg Parker wrote: > From: Greg Parker <gpar...@apple.com> > Subject: Re: ARC and Singletons > To: Kyle Sluder <kyle.slu...@gmail.com> > Cc: Cocoa Dev <cocoa-dev@lists.apple.com> > Message-ID: <bb621453-c3f5-4338-b2a6-ff120144e...@apple.com> > Content-Type: text/plain; charset=iso-8859-1 > > On Aug 1, 2011, at 9:02 PM, Kyle Sluder wrote: >> if we had class storage (which in practice would be no different from >> static global variables except for scope), class methods would still >> be appropriate for a different set of tasks. > > Not necessarily. Class variables could be defined differently from global > variables. If a class variable were defined in the natural way, as an > instance variable for the class instance described by the metaclass, then > class variables would be inherited in the same way that instance variables > are. A subclass object would have its own copy of its superclass's variables, > just like a subclass instance object has its own copy of its superclass > instance's variables. > > -- > Greg Parker gpar...@apple.com Runtime Wrangler _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
