If I have this in my .h
file:
int index;
And then in the .m
file I have:
if (index == nil)
The variable is technically undefined (may have any value) before you assign it a value. Most likely, it will be equal to zero. Also, both nil and NULL are defined to zero. However, this comparison is not recommended. You should only use nil when comparing pointers (it is not intended to be used with primitives).
There is no such thing as "nil" for ints. That's an object value. As for what variables are initialized to by default:
Note that the first rule above also applies to local object variables. They will not be nil-initialized for you. (Instance variables with object types will be, though.)
nil is a specific value reserved for Objective-C object pointers. It is very similar to NULL (0) but has different semantics when used with message passing.
local primitive data types like int's are not initialized in Objective-C. The value of index will not be defined until you write to it.
void foo () {
//initialize local variable
int x = 5;
}
//initialise static variable
static int var = 6;
The value of an integer that hasn't yet been assigned depends on its declaration - an int
with static storage duration is zero if you don't assign it anything else. An int
with automatic or allocated storage duration could have any value if you don't explicitly initialize it.
By the way, putting an object declaration in your header like that is bound to cause you pain later.