Re: strong and readonly
Re: strong and readonly
- Subject: Re: strong and readonly
- From: Rick Mann <email@hidden>
- Date: Thu, 12 Apr 2012 01:18:21 -0700
On Apr 12, 2012, at 0:50 , Quincey Morris wrote:
> The "strong" or "weak" on the @property is indeed an implementation detail in that it affects the implied declaration of a *synthesized* ivar, and the implied memory management protocol with a *synthesized* setter method. In that sense, it "really" shouldn't be on the @property but on the @synthesize instead, but that's not going to happen, in part because @synthesize is being generally de-emphasized these days.
It'd sure be nice to write
@synthesize foo = __strong mFoo (or foo or _foo or whatever your convention is).
I wonder if NOT having that in the property declaration keeps it from being visible to the compiler when it needs to be.
--
Rick
_______________________________________________
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