Next: Exceptions Tutorial, Previous: Interpretation and Compilation Semantics and Immediacy Tutorial, Up: Tutorial
' word
gives you the execution token (XT) of a word. The XT is a
cell representing the interpretation semantics of a word. You can
execute this semantics with execute
:
' + .s 1 2 rot execute .
The XT is similar to a function pointer in C. However, parameter passing through the stack makes it a little more flexible:
: map-array ( ... addr u xt -- ... ) \ executes xt ( ... x -- ... ) for every element of the array starting \ at addr and containing u elements { xt } cells over + swap ?do i @ xt execute 1 cells +loop ; create a 3 , 4 , 2 , -1 , 4 , a 5 ' . map-array .s 0 a 5 ' + map-array . s" max-n" environment? drop .s a 5 ' min map-array .
You can use map-array with the XTs of words that consume one element more than they produce. In theory you can also use it with other XTs, but the stack effect then depends on the size of the array, which is hard to understand.
Since XTs are cell-sized, you can store them in memory and manipulate
them on the stack like other cells. You can also compile the XT into a
word with compile,
:
: foo1 ( n1 n2 -- n ) [ ' + compile, ] ; see foo
This is non-standard, because compile,
has no compilation
semantics in the standard, but it works in good Forth systems. For the
broken ones, use
: [compile,] compile, ; immediate : foo1 ( n1 n2 -- n ) [ ' + ] [compile,] ; see foo
'
is a word with default compilation semantics; it parses the
next word when its interpretation semantics are executed, not during
compilation:
: foo ( -- xt ) ' ; see foo : bar ( ... "word" -- ... ) ' execute ; see bar 1 2 bar + .
You often want to parse a word during compilation and compile its XT so
it will be pushed on the stack at run-time. [']
does this:
: xt-+ ( -- xt ) ['] + ; see xt-+ 1 2 xt-+ execute .
Many programmers tend to see '
and the word it parses as one
unit, and expect it to behave like [']
when compiled, and are
confused by the actual behaviour. If you are, just remember that the
Forth system just takes '
as one unit and has no idea that it is
a parsing word (attempts to convenience programmers in this issue have
usually resulted in even worse pitfalls, see
State
-smartness—Why it is evil and How to Exorcise it).
Note that the state of the interpreter does not come into play when
creating and executing XTs. I.e., even when you execute '
in
compile state, it still gives you the interpretation semantics. And
whatever that state is, execute
performs the semantics
represented by the XT (i.e., for XTs produced with '
the
interpretation semantics).
Reference: Tokens for Words.