Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!husc6!endor!siegel
From: siegel@endor.uucp (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: THINK Pascal debugger (Re: THINK C Debugger)
Message-ID: <4716@husc6.harvard.edu>
Date: 14 Nov 90 23:03:35 GMT
References: <1990Nov13.223209.16268@midway.uchicago.edu> <25759@dartvax.Dartmouth.EDU>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 28

In article <25759@dartvax.Dartmouth.EDU> Jim.Matthews@dartmouth.edu (Jim Matthews) writes:
>In article <1990Nov13.223209.16268@midway.uchicago.edu>,
>gft_robert@gsbacd.uchicago.edu writes:

>work.  Part of that has to do with the kludgy way TP runs programs in its
>own heap,

	Actually, it's one of the more elegant pieces of work that I've 
seen: a context switch that predates MultiFinder...
>
>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.

	The Observe window is pretty handy for those (like you) with a
minimalist philosophy; you can type expressions into the Observe window,
and unlike the THINK C debugger, the expressions will be evaluated in the
current context, rather than the context in which they were entered.

R.



 Rich Siegel	Software Engineer	Symantec Languages Group
 Internet: siegel@endor.harvard.edu	UUCP: ..harvard!endor!siegel

If you have telekinetic powers, raise my hand.