Re: strong and readonly
Re: strong and readonly
- Subject: Re: strong and readonly
- From: Thomas CLEMENT <email@hidden>
- Date: Thu, 12 Apr 2012 08:58:25 +0200
On 12 avr. 2012, at 00:36, David Duncan < email@hidden> wrote: On Apr 11, 2012, at 3:23 PM, Rick Mann wrote: It doesn't really make sense to specify a property as both strong and readonly, right? strong/weak only make sense in the setting of a property, not the getting, right?
If you are going to internally redeclare the property as readwrite, then the memory management declaration (strong/weak/etc) needs to match. Hence the "strong, readonly" property.
Isn't that exposing implementation details of the class that have nothing to do in its public header?
Thomas |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden