Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!rochester!uhura.cc.rochester.edu!uhura!saaf From: saaf@joker.optics.rochester.edu (Lennart Saaf) Newsgroups: comp.sys.mac.hypercard Subject: Re: debuggers for XCMD's Message-ID: Date: 14 Aug 90 13:21:42 GMT References: <12767@june.cs.washington.edu> <12780@june.cs.washington.edu> Sender: news@uhura.cc.rochester.edu Organization: The Institute of Optics, University of Rochester Lines: 26 In-reply-to: moore@cs.washington.edu's message of 14 Aug 90 08:24:57 GMT >>>>> On 14 Aug 90 08:24:57 GMT, moore@cs.washington.edu (Charles Moore) said: CM> In article <12767@june.cs.washington.edu>, I write: > > What debuggers are people out there using for their XCMD's? What do > people recommend? > As this is a subject that might generate a lot of > responses and as the results might be of general interest, please ... CM> Boy, was I wrong! I have yet to receive a single response! Doesn't CM> anybody out there have a recommendation for an XCMD debugger? Or am CM> I the only person left in the world who still writes buggy code? CM> Charles XCMDs are code resources, so I believe that debugging the source is out of the question, at least for any of the Think environments. You will have to resort to MacsBug or TMON. Len -- ------------------------------------------------------------------------ | Len Saaf, The Institute of Optics, Univ. of Rochester, Rochester, NY | | Internet: saaf@joker.optics.rochester.edu Bitnet: SAAF@UOROPT | ------------------------------------------------------------------------