<(SUBMODULE module [tuple])>
This statement is used at the beginning of all other template header or source files belonging to module (which has to be a LISP symbol). Note that it also appears in the master template source file, because all the master template source file peculiarities are handled in the DEFAULTMETHODS statement (see below), and therefore there is no need for a special MODULE statement to be used in the master template source file. The SUBMODULE statement loads the VOOPS save file module.vop and the optional tuple file (which has to be a vospec, see Section 6.1.2). This feature is useful, if UNFUG should be used for its genuine purpose also, i.e. looping around certain code templates substituting keywords from the tuple file see Section 5.5. A documentation comment is output stating that this submodule's documentation belongs to module.