Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sunybcs!boulder!hao!oddjob!gargoyle!ihnp4!ihlpg!timborn
From: timborn@ihlpg.UUCP
Newsgroups: comp.lang.forth
Subject: Debugging Aids for Forth
Message-ID: <3623@ihlpg.ATT.COM>
Date: Tue, 11-Aug-87 02:57:30 EDT
Article-I.D.: ihlpg.3623
Posted: Tue Aug 11 02:57:30 1987
Date-Received: Wed, 12-Aug-87 07:08:14 EDT
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 23

My fondness for Forth has waned in recent months due to the (apparent)
lack of debugging tools available.  I guess I'm spoiled by my UNIX
environment, with tracers & symbolic debuggers and all.  When I run
into trouble with Forth on my micro, it seems I have to exsert a great 
amount of effort tracing words to find the problem.

I appeal to those of you who have so much more experience in this area
than I: what are the "tricks of the trade"?  The day to day debugging
tools & techniques that you obviously take for granted that make your
life so much more productive (in Forth) than mine?

I venture to guess that there are others who follow this group who are
reasonably intelligent folks who just haven't caught on to thinking
in Forth.  I open myself up to your collective wisdom - I dare you to
show me that Forth can be used without going bald from banging ones head
against the walls.

"Ah so, Grasshopper.  You have much to learn".

Tim Born
...ihnp4!ihlpg!timborn

{insert standard disclaimer here}