Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!bu.edu!dartvax!news
From: Jim.Matthews@dartmouth.edu (Jim Matthews)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C Debugger
Message-ID: <25759@dartvax.Dartmouth.EDU>
Date: 14 Nov 90 18:15:07 GMT
References: <1990Nov13.223209.16268@midway.uchicago.edu>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: Jim.Matthews@dartmouth.edu (Jim Matthews)
Organization: Dartmouth Software Development
Lines: 34

In article <1990Nov13.223209.16268@midway.uchicago.edu>,
gft_robert@gsbacd.uchicago.edu writes:
> 
> Speaking of the THINK C debugger:
> 
> It's a pretty nice graphical source-level debugger.  BUT it seems really 
> kludgy in many ways, at least compared to the THINK Pascal debugger.

Just to be contrary, (and in case Symantec is listening), I'll offer the 
opposite opinion :-).  I think the THINK C debugger is one of the best 
parts of THINK C, while LightsBug is one reason I use MPW for my Pascal 
work.  Part of that has to do with the kludgy way TP runs programs in its
own heap, but I also find the TC debugging interface to be more productive.

> My main beef is having to type in the variables I wish to examine....
..
> Much better is THINK Pascal's method of having all variables immediately
> available for examination....

I don't usually type my variables into the THINK C debugger -- it's easier 
to select them and type Cmd-D.  Think Pascal shows all variables 
automatically, but that hides the few I care about among the many I don't.
The numerous icons and subpanes in the LightsBug window are an additional
distraction.

It would be nice if the THINK C debugger could save and restore the state
of the Data windows, but it works well enough that I usually don't have
to walk through the code more than once or twice.  My biggest gripe is
that it doesn't save the Source and Data window positions, so I always
have to rearrange them to get a good view of my source.

Jim Matthews
Dartmouth Software Development
--