I would lean towards
if (object == nil)
but I've noticed in some tutorials the use of
if (nil == object)
Is this just a style thing, or is there some justified rationale for using either format?
views:
120answers:
2
+2
A:
The if (nil == object) version protects you better in case you accidentally put = instead of ==.
Jim
2010-06-16 12:28:04
+10
A:
This is typically done to prevent using an assignment operator instead of a comparison operator. If you accidently typed this for instance:
if (object = nil)
It may compile but it isn't what you intended.
By using the second form you will ensure a compile time error if you mistype it, as nil cant be used as the left operand in assignments.
Please note I'm not an objective C programmer, but this question is generic to a lot of languages.
Neil Aitken
2010-06-16 12:29:14
OK. It seems to me though that if you have enough presence of mind to put the nil first (in case you type a single =), you've already reminded yourself to do the double ==. Thanks.
Bill
2010-06-16 12:35:42
Indeed, I usually don't bother with the second form, but some people prefer it just to be safe, and prevent sometimes hard to find bugs.
Neil Aitken
2010-06-16 12:41:15