Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ncar!midway!news
From: gft_robert@gsbacd.uchicago.edu
Newsgroups: comp.sys.mac.programmer
Subject: THINK C Debugger (was Re: Looking for a Debugger.)
Message-ID: <1990Nov13.223209.16268@midway.uchicago.edu>
Date: 13 Nov 90 23:26:19 GMT
Sender: news@midway.uchicago.edu (News Administrator)
Organization: University of Chicago Graduate School of Business
Lines: 25

-------- 

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.

My main beef is having to type in the variables I wish to examine.  I HATE
this, particularly since these variable names aren't kept around between
runnings of the program in development.  This considerably lengthens the
edit-run-debug-edit cycle.  (Or does someone know a way to keep them around?).

Much better is THINK Pascal's method of having all variables immediately
available for examination, and having variables for different procs in
different places in the debugger window.  In THINK C I tend to end up with 5
windows each named "*theTable" (for example), each tracking a variable thru the
call chain.

Robert

============================================================================
= gft_robert@gsbacd.uchicago.edu * generic disclaimer: * "It's more fun to =
=            		         * all my opinions are *  compute"         =
=                                * mine                *  -Kraftwerk       =
============================================================================