Kevin, I think that the answer is that your testing may not reveal a problem, but somewhere, somewhen, somebody will find it. And it will happen when you are trying to make a critical release upon which the life of your company depends, or worse, upon which the life of a patient depends, given that you're doing medical stuff. Fix it now, when you can see it, when you haven't released it, when you still remember it.
In your testing, your hardware and software configuration leaves your memory configuration in a place such that the global flag reference finds real physical memory. In another time (newer or older OS release) another place (newer or older hardware platform) another user (somebody with more/less software or hardware) the flag will be located where there isn't memory and you will crash hard. Or worse, it might just happen to reference an I/O register that changes when read. -andy -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
