Re: Memory management on returning nil in init
Re: Memory management on returning nil in init
- Subject: Re: Memory management on returning nil in init
- From: Scott Anguish <email@hidden>
- Date: Wed, 23 Jun 2010 22:42:20 -0400
Yes, that works as well. The reason we’ve advocated the longer form is that it is clearer what is happening to those who are not as intimate with the quirks like this.
I also recall reading (but don’t quote me on this) that the longer form generates less instructions. I can’t recall where though.
In documentation you won’t see (( for the above reason (clearer) and because it was likely we’d get typo reports.
On Jun 23, 2010, at 4:27 PM, Charles Srstka wrote:
> On Jun 23, 2010, at 3:00 PM, Jens Alfke wrote:
>
>> Yes. Any expression of the form
>>
>> if(A = B)
>>
>> i.e. an assignment directly inside an if, will result in a warning that this looks confusingly like a comparison.
>
> If you prefer the if(A = B) syntax, though, this can be worked around by using double parentheses, i.e.
>
> if((A = B))
>
> Charles
_______________________________________________
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