Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!ucbcad!ucbvax!decvax!tektronix!tekcrl!tekgvs!keithe
From: keithe@tekgvs.TEK.COM (Keith Ericson)
Newsgroups: comp.lang.forth
Subject: Re: Debugging Aids for Forth
Message-ID: <2574@tekgvs.TEK.COM>
Date: Tue, 18-Aug-87 13:54:35 EDT
Article-I.D.: tekgvs.2574
Posted: Tue Aug 18 13:54:35 1987
Date-Received: Fri, 21-Aug-87 06:49:05 EDT
References: <3623@ihlpg.ATT.COM>
Reply-To: keithe@tekgvs.UUCP (Keith Ericson)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 14

In article <3623@ihlpg.ATT.COM> timborn@ihlpg.ATT.COM (Tim Born) writes:
>My fondness for Forth has waned in recent months due to the (apparent)
>lack of debugging tools available...
>
>I appeal to those of you who have so much more experience in this area
>than I: what are the "tricks of the trade"?

I haven't had a chance to study it yet, but the most recent edition of
FORTH DIMENSIONS (Volune IX, Number 2) has an article, with source, of a
test environment which allows one to decide, at compile time, whether or
not debugging code should be compiled into the definitions. It appears
similar to the #ifdef DEBUG technique.

keith