Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!bloom-beacon!eru!hagbard!sunic!kth.se!cyklop.nada.kth.se!news
From: d88-jwa@byse.nada.kth.se (Jon W{tte)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK Pascal debugger (Re: THINK C Debugger)
Message-ID: <1990Nov17.164212.8825@nada.kth.se>
Date: 17 Nov 90 16:42:12 GMT
References: <1990Nov13.223209.16268@midway.uchicago.edu> <25759@dartvax.Dartmouth.EDU> <4716@husc6.harvard.edu> <1990Nov15.210134.7758@svc.portal.com> <4743@husc6.harvard.edu>
Organization: Royal Institute of Technology, Stockholm, Sweden
Lines: 25

In article <4743@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes:

>In Observe, you can type in "hpb.ioActCount", and there you have it.
>The THINK C approach to viewing structures does have its advantages,
>but so does the THINK Pascal approach.

Well, in _my_ THINK C 4.0 I can type (for instance) "(**hTE).selStart",
and get it... Is this a bug ? Am I entitled to a refund ? ;-)

#define _FLAME_

The THINK C environment would be a dream if the DARNED DEBUGGER WOULD
KEEP BREAKPOINTS AND WATCHED VARIABLES, D*MMIT !!!!!

#endif /* _FLAME_ */

Better support for external editors (like, say, Alpha (Yes, Pete, I'm
on my way to the exchange office)) would be nice, as would compilation
in the background and a list of encounbtered errors, not just a halt
after the first error. (ACtually, I think this is what Saddam is
_really_ after ;-)

							h+
h+@nada.kth.se
"Moof!(tm)"