Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu.UUCP
Newsgroups: comp.sys.mac
Subject: Re: LSC and the bugs from hell
Message-ID: <21523@ucbvax.BERKELEY.EDU>
Date: Fri, 30-Oct-87 03:13:32 EST
Article-I.D.: ucbvax.21523
Posted: Fri Oct 30 03:13:32 1987
Date-Received: Sat, 31-Oct-87 17:48:15 EST
References: <10620014@hpfclm.HP.COM> <598@analog.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Organization: School of Education, UC-Berkeley
Lines: 22

Here is an opinion you don't see everyday: I think Macsbug is better than
TMON.

Scott Knaster's "How to Write Macintosh Software" raves about TMON.  A
few months ago I took an afternoon out and sat down, read the TMON
manual from cover to cover, and tried to actually use it. I found it
clumsy to use, I couldn't make it do what I wanted, and the user
interface was so complicated and so lacking in self-consistancy that I
had to spend an immense amount of time just fighting TMON to do simple things.

In addition, I'd already built a large personal set of debugging tools
on top of DebugStr(), and the TMON documentation lead me to believe
that TMON couldn't handle the DebugStr() tooltrap.

Conclusion:
Please show me the error of my ways. Mail me a description of how
TMON makes you more productive. I'll consolidate and repost to the net.


--- David Phillip Oster            --A Sun 3/60 makes a poor Macintosh II.
Arpa: oster@dewey.soe.berkeley.edu --A Macintosh II makes a poor Sun 3/60.
Uucp: {uwvax,decvax,ihnp4}!ucbvax!oster%dewey.soe.berkeley.edu