But yes - I admit that CW9 was not the feature upgrade that CW 7 & 8 were. My guess is that Palm has some massive changes looming and Metrowerks is fighting to keep on top of them.

Huh? Object Library for Palm OS, ARM compiler, Palm OS 68K linker, docking windows, a stab at code completion, error lookup window, enhanced debugger features anyone? :) You do realize that your can download an arbitrary group of PRC and PDB files with your program now, and that you can have the debugger simulate a no-global launch so you can find nasty problems with launch codes that don't support global variables.


From my perspective, we implemented a lot more features in V9 than we did in either V7 or V8.

I find sometimes the debugger simply won't tell me the true value of variables to the point where I can't debug. And this is with all optimizations off. I can understand the old bug in which you have many instances of the same name and it doesn't know which one to show you, but often, it just shows a wacky value for a variable even though the real code knows the real value. This problem *seems* worse in CW9 than CW8, but it could be my imagination.

This is a situation where good examples of the debugger misbehaving are worth their weight in gold to us. I just don't see this happening in the code I'm debugging -- generally a lot of the samples that come with CW, plus my own code.


--
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/

Reply via email to