Xref: utzoo comp.sys.mac.programmer:9793 comp.sys.mac.hypercard:2607
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!gft_robert@gsbacd.uchicago.edu
From: gft_robert@gsbacd.uchicago.edu
Newsgroups: comp.sys.mac.programmer,comp.sys.mac.hypercard
Subject: Debugging XFCN's/XCMD's
Message-ID: <5870@tank.uchicago.edu>
Date: 17 Oct 89 21:48:19 GMT
Sender: news@tank.uchicago.edu
Organization: University of Chicago Graduate School of Business
Lines: 28


I'm writing a somewhat tricky text-processing XFCN of about 500 lines and I
need some hints about how to debug XFCN's in general.  The XFCN makes almost no
ROM calls, so it's hard to see how far I've gotten in it before it crashes
(which it does).

I'm using THINK Pascal.  Is there any way that one can use the source-level
debugger when writing XFCN's?  I doubt it very much, but just thought I'd ask. 
Would HyperTMON (which I've never seen) be of any help at all?  If I were doing
it with MPW Pascal/TML Pascal, would it be possible to use SADE?

Failing that, what are the tricks you use when debugging complicated XFCN's? 
Do you write out diagnostic info to the HyperCard screen?

As a last resort, how would one go about debugging it from the machine level
(MacsBug, etc.).  I ask, because I'm not sure about the low-level interaction
between my XFCN and HyperCard itself, and want to know what I should expect to
be seeing.

Any info much appreciated!

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