> hmm.. CW -> gcc is a piece of cake in comparison to the other way
> around :) gcc -> CW is a nightmare, as you need to recreate all the
> resources in constructor and get the resource #defines correct :)
gcc -> CW porting is fairly easy when using the PilRC plugin, as you
should know, Aaron.
> #define appCreator 'Razr'
> #define appVersionNum 0x01
>
> thats how i have been doing it since day one.. is there a need to
> store them in a global variable? they are obviously not going to
> change, so might be best to declare as constants :)
To use C++ constants, modify your header to say
static const UInt32 appCreator = 'Razr';
static const Int16 appVersionNum = 0x01;
C++ allows the compiler to treat these as true constants -- without the
static, they could have scope outside the current file, so the compiler
creates data for them. GCC doesn't do the optimization that CW does
with replacing the constant reference with its value when they are
non-static.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
