Re: Cocoa-dev Digest, Vol 8, Issue 597
Re: Cocoa-dev Digest, Vol 8, Issue 597
- Subject: Re: Cocoa-dev Digest, Vol 8, Issue 597
- From: Martin Stanley <email@hidden>
- Date: Fri, 05 Aug 2011 11:20:15 +0300
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 <email@hidden>
> Subject: Re: ARC and Singletons
> To: Kyle Sluder <email@hidden>
> Cc: Cocoa Dev <email@hidden>
> Message-ID: <email@hidden>
> 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 email@hidden Runtime Wrangler
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden