Updated answer: You can make use of the z and t modifiers to handle NSInteger and NSUInteger without warnings, on all architectures. You want to use %zd for signed, %tu for unsigned, and %tx for hex. This information comes courtesy of Greg Parker. Original answer: The official recommended approach is to use %ld as your … Read more
You get this warning if you compile on OS X (64-bit), because on that platform NSInteger is defined as long and is a 64-bit integer. The %i format, on the other hand, is for int, which is 32-bit. So the format and the actual parameter do not match in size. Since NSInteger is 32-bit or … Read more
NSIntegers are not objects, you cast them to long, in order to match the current 64-bit architectures’ definition: NSString *inStr = [NSString stringWithFormat: @”%ld”, (long)month];
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 integer 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 … Read more