Xref: utzoo comp.sys.mac.programmer:9854 comp.sys.mac.hypercard:2618
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: Re: Debugging XFCN's/XCMD's
Message-ID: <5917@tank.uchicago.edu>
Date: 20 Oct 89 14:17:37 GMT
Sender: news@tank.uchicago.edu
Distribution: na
Organization: University of Chicago Graduate School of Business
Lines: 17

In article <717@lclark.UUCP>, dan@lclark.UUCP (Dan Revel) writes...
 
>From your description I would say that your best bet would be to
>debug your code *before* making it into an XCMD/XFCN.  You could
>even mock-up a program which calls your routine the way Hypercard
>would.  Of course this won't work if you intend to make call-backs
>or pass messages to Hypercard.

That's indeed the problem: I'm using a lot of callbacks.  Oh well.



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