🚀 go-pugleaf

I only used C++ under CW 5.3. Now that I am working on Java 1.1
stationary projects on the Mac with CW Pro 6.0, I can see the problem
people are experiencing.

If the speed issue is new to CW 6, and did not exist in 5.3, then I
would think the problem lies with CW 6, and not Apple, Mac OS
limitaitons, etc.

Are ther any 5.3 users having problems with slow java debuggers?

Cheers,

-Navid.

In article <ejalbert-3FBDD1.13140019102000@nntp.stanford.edu>, Eric
Albert <ejalbert@stanford.edu> wrote:

> In article <B61484D4.A1B3%sroy@mac.com>, Steve Roy <sroy@mac.com> 
> wrote:
> 
> > 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.
> 
> The speed isn't really Metrowerks' fault, or that of the Java team at 
> Apple.  Sun's debugging API reflects Sun's belief that TCP/IP is the 
> best solution for everything, which isn't really always the case.  In 
> this case, you've got two processes running on an OS with pretty poor 
> process management and a networking architecture that doesn't appear to 
> be optimized for communication between local apps.  Those are two things 
> that are much improved on Mac OS X, fortunately.
> 
> Though I don't have much experience with the CodeWarrior debugger -- 
> println's and the mrj dcmd can actually accomplish quite a lot if you 
> need them to :) -- I suspect that remote debugging may perform 
> reasonably close to local debugging, if not better, since you don't have 
> the overhead of the process switching.  Give that a shot if you can set 
> two machines up next to each other.
> 
> -Eric