> I don't know what other methods have been mentioned, but you can get the
> effect of globals by defining a structure containing all your data,
> allocating and initializing it in dynamic RAM, then stashing a pointer to it
> in a feature. If you do this in response to all launch codes, your app can
> be written to not care whether globals are available or not.
which is exactly what i have mentioned previously..
> > Globals use space on the dynamic heap, and can't be used in certain
> > circumstances anyway, so what other ways do we have of implementing them...
> > (I know Aaron recently suggested a method, but are there others?)
^^^^
i believe it is good practice this way, however, it still is global
data :)) some would argue throwing it in a feature is a bad thing
too.. :P more holy wars..
you *could*, if you got desperate and needed more memory for your
globals store them inside a database :) read the record, get your
globals, write the record (save em)
:P
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
