Xerox Nuvera 100, Software Manual

Page: 57 / 498

PDL principles and procedures
Using LCDS Print Description Language 1-29
Comments
Comments are optional statements you may include in the
source file to identify sections of the JSL, describe selected PDL
commands and their functions, or provide messages for anyone
who modifies the JSL later. The system does not perceive these
comments as commands and ignores them.
Comments may appear anywhere within the JSL and may
consist of multiple records. Comments must be preceded by the
character sequence slash asterisk (/*), and terminated by the
character sequence asterisk slash (*/). For example:
/*System commands are coded here.*/
Nested comments A comment may also be nested within another comment. There
is no practical limit to the level of nesting possible, as long as
each nested comment is preceded by a slash and an asterisk (/*)
and succeeded by an asterisk and a slash (*/). An acceptable
nested comment format is as follows:
/*
comment
/*
nested comment
*/
*/
Note that the illustration above ends with two */ markers: the first
for the nested comment and the second for the main comment.
Ending a JSL
A JSL terminates with the END command. When you are
finished constructing your JSL, you must let the system know
you are finished by entering the END; command, as shown
below. This also applies to CMEs, PDEs, TSTs, and
STOCKSETs you are coding.
END;
What may follow
the END;
command
After you end a JSL, you may still code certain items following
the END; command.
Subsequent JSLs: Following the END; command for one JSL,
you may code additional JSLs. If one JSL is to follow another,
the next command after the END; command should be another
“JDL” command.