#nsinteger

Fixed When to use NSInteger vs. int #dev #it #asnwer

When to use NSInteger vs. int

When should I be using NSInteger vs. int when developing for iOS? I see in the Apple sample code they use NSInteger (or NSUInteger) when passing a value as an argument to a function or returning a value from a function.

- (NSInteger)someFunc;... - (void)someFuncWithInt:(NSInteger)value;...

But within a function they’re just using int to track a value

for (int i; i…

How to: When to use NSInteger vs. int

When to use NSInteger vs. int

When should I be using NSInteger vs. int when developing for iOS? I see in the Apple sample code they use NSInteger (or NSUInteger) when passing a value as an argument to a function or returning a value from a function.

- (NSInteger)someFunc;... - (void)someFuncWithInt:(NSInteger)value;...

But within a function they’re just using int to track a value

for (int i; i…

You usually want to use NSInteger when you don't know what kind of processor architecture your code might run on, so you may for some reason want the largest possible int type, which on 32 bit systems is just an int, while on a 64-bit system it's a long.

I'd stick with using NSInteger instead of int/long unless you specifically require them.

NSInteger/NSUInteger are defined as *dynamic typedef*s to one of these types, and they are defined like this: