🚀 go-pugleaf

In article <1996Mar11.202751.4171@news.huji.ac.il> mslamm@pluto.mscc.huji.ac.il (Zvi Lamm) writes:
   1. How can you direct the output of a GML macro to a file [...]
   2. How can one process the end tags?  [...]

Grab the DCF manuals, and check out the .WF [Write to File] control word.
If you are lucky and your GML library is not already exploiting .WF, then
you should be able to use this as a way to spit information out into a "side
file".  You can use the .DD [Define Data File-ID] control to switch .WF
amongst multiple files.

Or, you might try using .MG [Message] to write your own "error" messages,
since messages are segregated (by DCF) from the main-line output.

APF macros for end tags are specified the same way as for begin tags, using
the .AA [Associate APF] control.  E.g., if BEGIN is the name of the macro
for the begin tag and END is the name of the macro for the end tag, then:

		.aa foo BEGIN END

will associate BEGIN with the :foo. tag and END with the :efoo. tag.  You
can override the scanning rules for either tag by enclosing the rules in
parens after the macro names, e.g.,

		.aa foo BEGIN (rules) END (rules)

Again, consult the DCF manuals.  There used to be a really super manual that
explained the implementation details of the Starter Set library, which was
an excellent "learn by example" introduction to GML and APF macros.  I don't
know if it is still in print, though...

--
      John A. Pershing Jr.                      pershng @ watson.ibm.com
      IBM Research, Yorktown Heights