Example 18 (from the User Manual) is an expanded version of Example 17,
with the print iterator and local functions called as macros.
Compare this example with Code Sample 6 (above) to see just how much
simpler your code can be when you switch to the print iterator.

This function uses the the print iterator and displays the value of every
System Constant. Compare this example with Code Sample 9 to see how much
"cleaner" your code looks when you use the print iterator.

This script tests the new IIF loader opcodes by creating an in-memory IIF image containing
one global function record, one local function record, and one End-of-Data record. There is one
optional argument for this script that, when present, will add an auto-start string to the
End-of-Data record. The MEMORY-MACRO ("m@") operator is used to execute the image and load the
two function definitions into their corresponding tables. If auto-start is requested, you will
see the output from the two functions after they execute. If auto-start is not requested,
the function names are listed to show they were added to the tables.

Load this file to restore the default macro definitions. This has been superceeded
by the "#restore" outer-interpreter directive, but it is still a good example of
a script file that does nothing other than define macros for interactive use.