Exceptions To The Style Conventions; Conventions Specific To This Manual - HP TACL Programming Manual

Exceptions to the Style In a few situations, the preceding style conventions do not produce optimal results.
Conventions For example, an #OUTPUT call that continues on a second line includes leading spaces
in the display. Therefore, text that continues an #OUTPUT call should be left-justified.
For example:
The second line of the #OUTPUT call is not indented two spaces.
In such cases, the examples in this manual note the exception and do not follow the
style conventions.
Conventions Specific to The following additional conventions are used for consistency:
This Manual
For more information about expressions, see the TACL Reference Manual.
107365 Tandem Computers Incorporated
indented two spaces within the square brackets. Conditional text is indented
two spaces past the labels. For example:
[#CASE [errornumber]
|0|
#OUTPUT [filename] was purged
|OTHERWISE|
#OUTPUT [filename] could not be purged
#OUTPUT Error [errornumber]
]
[#IF [x] > 0 |THEN|
#OUTPUT This is a test; the text for this #OUTPUT call &
is longer than a single line.
]
The COMPUTE command and the #COMPUTE, #IF, and #LOOP built-in
functions accept expressions as arguments. When you supply a variable name as
all or part of an expression, you can enclose the variable name in square brackets
or omit the square brackets. Either way, TACL retrieves the contents of the
variable.
The examples in this manual include the square brackets, to show that the
statement uses the contents of the variable. This approach, however, requires
slightly more processing by TACL.
The examples in this manual are restricted to a line length of 62 characters (as
opposed to 80 characters for an edit file). There are several function calls in this
manual that are longer than 62 characters; these calls are enclosed in square
brackets or are joined by an ampersand character:
[#SET temp [#CONTIME [#FILEINFO/MODIFICATION/
[thisfile]]]
#SET temp [#CONTIME [#FILEINFO/MODIFICATION/
[thisfile]]]
Lines that have 80 characters or less can fit on one edit file line; if you join these
lines in your program, you can omit the surrounding square brackets or the
ampersand character.
An Overview of TACL
Style Conventions
&
1–3