Is there an issue to use int for class property?


Is there an issue to use int for class property?



When I started with Cocoa, I remember that I read somewhere that int/float and similar should not be used for class properties and to use NS* equivalents (like NSInteger).

Is there a real hidden issue here why would that be better or it was just a voluntary coding rule by a person where I read that (and I can't for the life of me find where was that)?

So, what is better:

@interface xx...      int myProp; @end 

or

@interface xx...      NSInteger *myProp; @end 



c# create an instance of an object from string

1:



Using link_to in a class in a Rails helper
The int version is fine, but NSInteger is preferred.


C++ extern class definition
NSInteger isn't an object and doesn't have to be referenced with a pointer — it's just a typedef that will allow the variable to be the native word size on both 32-bit and 64-bit computers.


Does visual documentation exist for the Zend Framework API?
So the best option would be:.
How can I add and remove a class on links using jQuery?
@interface SomeClass : NSObject {     NSInteger aNumber; @end  @implementation SomeClass - (id)init {     [super init];     number = 42; } @end 


I need a good analogy to make sense of Class methods vs. instance methods


class.upload.php getting error

2:



How can I change the color of a UIWindow from a separate class?
See this question.

NSInteger is architecture safe and is recommended from 10.5 onwards..



85 out of 100 based on 55 user ratings 955 reviews