Files
LithosAnanke/docs/reference/standards/ans94/dpansa15.htm
T
Claude 3de8427827 docs: the FORTH standards v4 is held to -- FORTH-79, FORTH-83, ANS Forth 1994 (#189)
Captain Bob, 2026-11-14: the standard first, in the order 79, 83, ANS, then v3; the texts in the repository
as references. FORTH-79 and FORTH-83 from the University of Vienna's FORTH archive (complang.tuwien.ac.at),
ANS Forth's final draft (dpANS) from Taygeta, as fetched, with their sources in
docs/reference/standards/README.md. Not pushed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-14 03:16:13 +00:00

280 lines
7.2 KiB
HTML

<HTML><HEAD>
<TITLE>DPANS94</TITLE>
</HEAD>
<BODY>
<table width=100%>
<tr>
<td align=left>
<a href=dpansa14.htm><img src=left.gif
width=26 height=26 align=ALIGN border=0></a>
<a href=dpansa16.htm><img src=right.gif
width=26 height=26 align=ALIGN border=0></a>
</td>
<td align=right>
<a href=dpans.htm#toc><img src=up.gif
width=26 height=26 align=ALIGN border=0></a>
<a name=A.15>Table of Contents</a>
</td>
</tr>
</table>
<p>
<hr size=4>
<H2>A.15 The optional Programming-Tools word set</H2>
These words have been in widespread common use since the earliest Forth
systems.
<P>
Although there are environmental dependencies intrinsic to programs
using an assembler, virtually all Forth systems provide such a
capability. Insofar as many Forth programs are intended for real-time
applications and are intrinsically non-portable for this reason, the
Technical Committee believes that providing a standard window into
assemblers is a useful contribution to Forth programmers.
<P>
Similarly, the programming aids
<a href=dpans15.htm#15.6.1.1280>DUMP</a>,
etc., are valuable tools even
though their specific formats will differ between CPUs and Forth
implementations. These words are primarily intended for use by the
programmer, and are rarely invoked in programs.
<P>
One of the original aims of Forth was to erase the boundary between
<B>user</B> and <B>programmer</B> - to give all possible power to anyone
who had occasion to use a computer. Nothing in the above labeling or
remarks should be construed to mean that this goal has been abandoned.
<P>
<hr>
<A name=A.15.6>
<H3>A.15.6 Glossary</H3>
</a>
<hr>
<A name=A.15.6.1.0220>A.15.6.1.0220 .S</A>
<P>
.S is a debugging convenience found on almost all Forth systems. It is
universally mentioned in Forth texts.
<P>
<hr>
<A name=A.15.6.1.2194>A.15.6.1.2194 SEE</A>
<P>
SEE acts as an on-line form of documentation of words, allowing modification
of words by decompiling and regenerating with appropriate changes.
<P>
<hr>
<A name=A.15.6.1.2465>A.15.6.1.2465 WORDS</A>
<P>
WORDS is a debugging convenience found on almost all Forth systems. It is
universally referred to in Forth texts.
<P>
<hr>
<A name=A.15.6.2.0470>A.15.6.2.0470 ;CODE</A>
<P>
Typical use: <code>: namex ... &lt;create&gt; ... ;CODE ...</code>
<P>
where namex is a defining word, and &lt;create&gt; is
<a href=dpans6.htm#6.1.1000>CREATE</a> or any user
defined
word that calls CREATE.
<P>
<hr>
<A name=A.15.6.2.0930>A.15.6.2.0930 CODE</A>
<P>
Some Forth systems implement the assembly function by adding an
<a href=dpans15.htm#15.6.2.0740>ASSEMBLER</a>
word list to the search order, using the text interpreter to
parse a postfix assembly language with lexical characteristics similar
to Forth source code. Typically, in such systems, assembly ends when a
word END-CODE is interpreted.
<P>
<hr>
<A name=A.15.6.2.1015>A.15.6.2.1015 CS-PICK</A>
<P>
The intent is to reiterate a dest on the control-flow stack so that it can be
resolved more than once. For example:
<PRE>
\ Conditionally transfer control to beginning of loop
\ This is similar in spirit to C's "continue" statement.
: ?REPEAT ( dest -- dest ) \ Compilation
( flag -- ) \ Execution
0 CS-PICK POSTPONE UNTIL
; IMMEDIATE
: XX ( -- ) \ Example use of ?REPEAT
BEGIN
...
flag ?REPEAT ( Go back to BEGIN if flag is false )
...
flag ?REPEAT ( Go back to BEGIN if flag is false )
...
flag UNTIL ( Go back to BEGIN if flag is false )
...
;
</PRE>
<P>
<hr>
<A name=A.15.6.2.1020>A.15.6.2.1020 CS-ROLL</A>
<P>
The intent is to modify the order in which the origs and dests on the
control-flow stack are to be resolved by subsequent control-flow words. For
example,
<a href=dpans6.htm#6.1.2430>WHILE</a> could be implemented in terms of
<a href=dpans6.htm#6.1.1700>IF</a> and CS-ROLL, as follows:
<PRE>
: WHILE ( dest -- orig dest ) POSTPONE IF 1 CS-ROLL ; IMMEDIATE
</PRE>
<P>
<hr>
<A name=A.15.6.2.1580>A.15.6.2.1580 FORGET</A>
<P>
Typical use: <code>... FORGET name ...</code>
<P>
FORGET assumes that all the information needed to restore the dictionary to
its previous state is inferable somehow from the forgotten word. While this
may be true in simple linear dictionary models, it is difficult to implement
in other Forth systems; e.g., those with multiple address spaces. For
example, if Forth is embedded in ROM, how does FORGET know how much RAM to
recover when an array is forgotten? A general and preferred solution is
provided by
<a href=dpans6.htm#6.2.1850>MARKER</a>.
<P>
<hr>
<A name=A.15.6.2.2531>A.15.6.2.2531 [ELSE]</A>
<P>
Typical use: <code>... flag [IF] ... [ELSE] ... [THEN] ...</code>
<P>
<hr>
<A name=A.15.6.2.2532>A.15.6.2.2532 [IF]</A>
<P>
Typical use: <code>... flag [IF] ... [ELSE] ... [THEN] ...</code>
<P>
<hr>
<A name=A.15.6.2.2533>A.15.6.2.2533 [THEN]</A>
<P>
Typical use: <code>... flag [IF] ... [ELSE] ... [THEN] ...</code>
<P>
Software that runs in several system environments often contains some
source code that is environmentally dependent. Conditional compilation - the
selective inclusion or exclusion of portions of the source code at
compile time - is one technique that is often used to assist in the
maintenance of such source code.
<P>
Conditional compilation is sometimes done with <B>smart comments</B> -
definitions that either skip or do not skip the remainder of the line
based on some test. For example:
<PRE>
\ If 16-Bit? contains TRUE, lines preceded by 16BIT\
\ will be skipped. Otherwise, they will not be skipped.
VARIABLE 16-BIT?
: 16BIT\ ( -- ) 16-BIT? @ IF POSTPONE \ THEN ; IMMEDIATE
</PRE>
<P>
This technique works on a line by line basis, and is good for short,
isolated variant code sequences.
<P>
More complicated conditional compilation problems suggest a nestable
method that can encompass more than one source line at a time. The
words included in the ANS Forth optional Programming tools extensions
word set are useful for this purpose. The implementation given below
works with any input source (keyboard,
<a href=dpans6.htm#6.1.1360>EVALUATE</a>,
<a href=dpans7.htm#7.6.1.0800>BLOCK</a>, or text file).
<PRE>
: [ELSE] ( -- )
1 BEGIN \ level
BEGIN
BL WORD COUNT DUP WHILE \ level adr len
2DUP S" [IF]" COMPARE 0=
IF \ level adr len
2DROP 1+ \ level'
ELSE \ level adr len
2DUP S" [ELSE]"
COMPARE 0= IF \ level adr len
2DROP 1- DUP IF 1+ THEN \ level'
ELSE \ level adr len
S" [THEN]" COMPARE 0= IF \ level
1- \ level'
THEN
THEN
THEN ?DUP 0= IF EXIT THEN \ level'
REPEAT 2DROP \ level
REFILL 0= UNTIL \ level
DROP
; IMMEDIATE
: [IF] ( flag -- )
0= IF POSTPONE [ELSE] THEN ; IMMEDIATE
: [THEN] ( -- ) ; IMMEDIATE
</PRE>
<P>
<hr>
<A href=dpans.htm#toc><IMG src="up.gif" ></A> Table of Contents
<BR>
<A href=dpansa16.htm><IMG src="right.gif" ></A>
Next Section
<P>
</BODY>
</HTML>