On Nov 30, 2009, at 12:41 AM, Kenny Leung wrote:
- Constants.h ---
extern const NSString *Suction;
- Constants.m ---
const NSString *Suction = @"Ball";
That should be:
extern NSString* const Suction;
and:
NSString* const Suction = @"Ball";
Th
Hi Tharindu.
I would create two files: Constants.h and Constants.m. Just like all C code,
you put your declarations in the .h and the definitions in the .m. They are
going to be very similar, except the .m defines the values, so it only happens
once. This is very important if you want to be abl
On Nov 29, 2009, at 9:30 AM, Tharindu Madushanka wrote:
> When defining constants can I keep all important constants in one file and
> use it all over the application, rather defining same constant in several .m
> files. This might be a basic question, but just could not figure out how to
> do th
On Nov 29, 2009, at 10:30 AM, Tharindu Madushanka wrote:
> When defining constants can I keep all important constants in one file and
> use it all over the application, rather defining same constant in several .m
> files.
Of course. You don't need to define classes or functions in source files,
Hi
When defining constants can I keep all important constants in one file and
use it all over the application, rather defining same constant in several .m
files. This might be a basic question, but just could not figure out how to
do this.
Thank you
Tharindu Madushanka
___
