🚀 go-pugleaf

Hi,

I am, to say it nicely, pretty upset with the state of Java debugging in
CodeWarrior 6 on Mac OS 9.

Debugging is waaaaaayyyy to slow, and the unsupported Metronub debugging
displays garbage instead of correct names in the Variables pane.

This means that the official debugging is unusable. I have tried it on many
machines. My main machine is a 9600/300. There I give Metrowerks the benefit
of the doubt, it's an older machine. But, I also tried it on a G3/233 and a
G4/400, and it's still unusable. I know Metrowerks know it's slow and it
will be better on Mac OS X, but what we need is a real solution right now.

And then the unsupported Metronub debugging. Why are variable names mangled?
I know it's unsupported, but goodness, you guys probably tried it. If you
saw that variable names were mangled like that, why the heck did you put it
on the CD?

It all comes down to: what are our options?

We are writing software for Mac OS 8/9. Although we have installed Mac OS X,
this is still a beta OS and we are not going to move our development
machines and build machines to OS X until it's final. This is just common
sense. At the very least, we will be writing software on Mac OS 8/9 for
another 6 months. What are we supposed to do in the meantime to debug our
code?

And don't tell me about putting System.err.println() statements in our code.
This is useful, but is not a debugging facility. Metrowerks is a serious
company and as such should have devised a serious plan to help their Mac
users.

Anyone has seen this mangled variable names problem? Am I missing something,
yet again?

Steve

-- 
Steve Roy <sroy@mac.com>