Re: Refactor To ARC suggest "weak" attribute for property
Re: Refactor To ARC suggest "weak" attribute for property
- Subject: Re: Refactor To ARC suggest "weak" attribute for property
- From: Lee Ann Rucker <email@hidden>
- Date: Fri, 05 Apr 2013 13:05:57 -0700
On Apr 4, 2013, at 11:50 PM, Andreas Grosam wrote:
> When using the "Refactor To Objective-C ARC" tool, Xcode suggests to convert from
>
> (@interface Foo)
>
> @property (atomic, readonly) NSError* error;
>
> to
>
> @property (weak, atomic, readonly) NSError* error;
>
>
> The property is "readonly". Thus, specifying a "weak" attribute makes no sense anyway. Why is Xcode suggesting to specify it weak?
Possibly because it has no way to tell that you won't re-declare it as readwrite - say, if it's something where the header has it as readonly but the .m file has readwrite - and when you do that, they have to match.
_______________________________________________
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