Re: Arg, lmao question - (int)getters/setters.

2008-12-23 Thread Robert Marini
Any stack variable (int, float, etc) won't be declared as a pointer. Recall that a variable containing a * indicates that it is, in fact, some address in memory that is being pointed to (hence a pointer). If we recall, then, that memory consists of a "stack" and a "heap" - the pointer sit

Re: Arg, lmao question - (int)getters/setters.

2008-12-23 Thread Graham Cox
On 23 Dec 2008, at 6:14 pm, aaron smith wrote: Sorry for the total newb here. What's the right way to create getters/setters for int's? Without the compiler warning about them? I've been trying: -(void)setSomeInt:(int)theInt { someInt=theInt; } -(int)someInt { return someInt; } Then c

Re: Arg, lmao question - (int)getters/setters.

2008-12-22 Thread Roland King
it looks as if you your class variable someInt declared as (int*), why? If you want an int, someInt should be declared as an int. aaron smith wrote: Sorry for the total newb here. What's the right way to create getters/setters for int's? Without the compiler warning about them? I've been tryi

Arg, lmao question - (int)getters/setters.

2008-12-22 Thread aaron smith
Sorry for the total newb here. What's the right way to create getters/setters for int's? Without the compiler warning about them? I've been trying: -(void)setSomeInt:(int)theInt { someInt=theInt; } -(int)someInt { return someInt; } Then calling it.. [myObj setSomeInt:1]; Usually I get