"YOUR kernel extensions"

your
This wordset is the place to add any additional primitives
you might wish. A set of words do already live here that
must be bound statically into the main pfe-object to
work out smart and nicely.
Tektronix CTE %version: bln_mpt1!5.17 % GNU LGPL
EXTENSIONS
* !> ( value [name] -- )

actually a synonym for TO but very common amongst
forth interpreters

your immediate synonym

* @> ( [name] -- value )

does fetch the value from the PFA of the named item, which
may be about everything, including a VARIABLE , VALUE
LVALUE , LOCALS| , VAR , DEFER , DOER , DOES>
and more.

your compiling primitive

* '> ( [name] -- xt )

get the execution-token, ie the CFA, of the word following.
This word is fully state-smart while the ANSI standard words
namely ' and ['] are not.

your compiling primitive

* INTO ( [name] -- pfa )

will return the parameter-field address of the following word.
Unlike others, this word will also return the address of
LOCALS| and local LVALUE - so in fact a TO A and
INTO A ! are the same. This word is most useful when calling
C-exported function with a temporary local-VAR as a return-place
argument - so the address of a local has to be given as an arg.
Beware that you should not try to save the address anywhere else,
since a local's address does always depend of the RP-depth -
EXIT from a colon-word and the value may soon get overwritten.
(see also TO )

your compiling primitive

EXTENSIONS &OF

no special info, see general notes

your immediate synonym

* .H2 ( value -- )

print hexadecimal, but with per-byte 0-padding
   0x0     -> 00
   0xf     -> 0f
   0x12    -> 12
   0x123   -> 0123
   0x1234  -> 1234
   0x12345 -> 012345

your ordinary primitive

* HERE-WORD ( char "name" -- )

a FIG-compatible WORD. Where ANSI says "skip leading delimiters"
this one acts as "skip leading whitespace". And it will not return
anything and have the string parsed to HERE

your ordinary primitive

EXTENSIONS FIG-WORD

no special info, see general notes

your loader code P4_xOLD