Re: [Obj-C] if (self) vs. if (self != nil)
Re: [Obj-C] if (self) vs. if (self != nil)
- Subject: Re: [Obj-C] if (self) vs. if (self != nil)
- From: Eeyore <email@hidden>
- Date: Sun, 26 Feb 2012 18:34:08 -0800
I think you can turn it off, but I think you can also use double-()'s to suppress it:
if ((self = [super init]))
On Feb 26, 2012, at 5:40 PM, Graham Cox wrote:
>
> On 27/02/2012, at 12:13 PM, William Squires wrote:
>
>> I prefer the "if (self = [super init])" combined form, myself.
>
>
> One potentially annoying thing about this form is that, if you compile with plenty of warnings on, such as the possible unintended assignment warning (if not, why not?) then this flags a warning.
>
> Apple recommend:
>
> self = [super init];
> if( self )
> {
> ...
> }
>
>
> Anyway, this seems to be one of those tiny trivial issues that people seem to get very religious about. It takes a second to type in any form, so what's the big deal?
>
> --Graham
>
>
> _______________________________________________
>
> 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
>
_______________________________________________
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