Hello,
As I don’t really know how iPhone OS does manage its memory, this question hit me today :
Considering a Static object is put into a portion of memory and won’t move from it until the end of the application, is it really safe to use Static ?
Logically, putting something into a fixed memory stack just makes it easier to read / hack, doesn’t it ?
That isn’t really how a static variable behaves.
It just means that the variable belongs to the class itself rather than any particular instance. Often, these will be initialised early on in the app’s execution, but they can certainly be changed at any point. There’s no particular security or performance issue when you declare something static.
Ok, thank you Andee.
If someone has gotten to the point where they can freely read and write to your app’s memory then you’re in trouble no matter how your memory is laid out.
I’m not there yet 
But honestly, considering how some guys are able to crack open a full operating system, I’m expecting everything.
The more we put hack resistances, the more tough hackers will be attracted, just for the challenge.
I prefer to prepare myself to every kind of hacking (game is not released yet, so I got some time).
This thread talks about interesting aspects of hacking, which include memory read on-the-fly.
And it seems to be the most popular way to hack a game, beyond DRM cracking : Back in the Sega Genesis / Super NES times, there were sold some cheat cartridge that did nothing but change memory values on the fly.
I’m just a noob in hack protection, but still, I feel that there is some internal way to screw vars readability.
Actually, hacking is killing indies, we have to care about it