Paul Rider wrote in a message to Mike Bilow:

 MB> Declare the variable with the ANSI C standard "volatile" keyword.

 PR> Yes, I've tried that. Provlem is the volatile int variable;
 PR> is in 1 class, and for some reason when I'm using an
 PR> (global) instance of that class's members which I have
 PR> declared volatile (in the original declaration... *.h file)
 PR> it's still optimizing it ala register. This is really
 PR> annoying as I don't want to shut off optimization just for
 PR> that, and If not then I spend alot of time calling/returning
 PR> from a functin that just returns the member's value anyways!
 PR>         . I suppose my attitude should be what's a
 PR> little xtra overhead, and a coupla hundred milli-seconds,
 PR> but it just bugs me...

That's a bad compiler bug, then.  If you want to force the compiler not to
enregister the variable, take its address.
 
-- Mike


---