>Whose assumptions? The compiler's or mine? I personnaly don't care where they're keypt. But can the CW debugger display the contents of variables if they get stored in registers? Would this be the reason of nonsense variables contents in the monitor window?
Seems to me I've prevented variables from being re-used or stored in registers by marking them as volatile. Might be useful for debugging a method or two.
Of course the debugger can display values when they are in registers. If you turn on the location column in the CW debugger, you'll see some variables with a register as the address, and some with the stack.
The issue is in the compiler -- it doesn't keep the names associated with the temporary variables created and destroyed during optimization, and even if it did, it might mean that you will have ten variables all with the same name assigned to different locations and valid at different parts of your program.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
