🚀 go-pugleaf

In article <7019@dartvax.UUCP> su@dartvax.UUCP (Peter Su) writes:
>Hi, in recent months I've lots of ads and hype about this product from
>Steve Jasik.  After reading the article in Mactutor, I'm wondering if anyone
>out there has acutally used this thing, and if so, is it really that good?
>
>I generally develop in LightSpeed C, and I'm trying to see whether I
>should wait for THINK to come up with a debugger, or go out and get
>"The Debugger" instead.

I'm using LightSpeedC and decided to pick up a copy of The Debugger when
it showed up at ComputerWare.  I tried it out but ended up going back to
TMON.  Why?  First the good points.  It is a very powerful debugger with
support for LightSpeedC symbols.  It provides a large set of breakpoints,
watchpoints and trap conditions.  It is supported by Steve on both Delphi
and CompueServe.  It uses the standard Mac interface (windows and scroll bars).

Now the bad points.  It is a memory hog.  It is still buggy (I was able
to crash The Debugger twice using the example program).  The user
interface is up to Steve Jasik's standards which means it is very bad.
It does not let you run direct from the LightSpeedC enviroment, you
have to load the Problem Program (the program your testing) after the Debugger
has been loaded (it's an application, not a resident program like TMON).
The manual is scattered and not very well orginized.

If you need the ultimate debugger, this is probably it.  But be prepared for
the high learning curve and the bugs.  

>
>Thanks!
>Pete


Jerry Whitnell                           It's a damn poor mind that can only
Communication Solutions, Inc.            think of one way to spell a word.
						-- Andrew Jackson