|
V+ 12.4 Release Notes |
This section presents the syntax of the keyword. The keyword is shown in uppercase and the arguments are shown in lowercase. The keyword must be entered exactly as shown. Parentheses must be placed exactly as shown. Required keywords, parameters, and marks such as equal signs and parentheses are shown in bold type; optional keywords, parameters, and marks are shown in regular type. In the example:
KEYWORD must be entered exactly as shown; in the SEE editor, you can abbreviate instructions to a length that uniquely identifies the keyword. The SEE editor automatically expands the instruction to its full length.
req.param1 must be replaced with a value, variable, or expression
= the equal sign must be entered
req.param2 must be replaced with a value, variable, or expression
OPT.KEYWORD can be omitted but must be entered exactly as shown if used
opt.param may be replaced with a value, variable, or expression but assumes a default value if not used
The keyword type (function, program instruction, and so on) is shown at the top of the page.
An abbreviated syntax is shown for some keywords. This is done when the abbreviated form is the most commonly used variation of the complete syntax.
This section gives a brief description of the keyword.
This section lists any restrictions on the keyword's use. If specific hardware or other options are required, they will be listed here.
The requirements for input and output parameters are explained in this section. If a parameter is optional, it will be noted here. When a command or instruction line is entered, optional parameters do not have to be specified and the system will assume a default. Unspecified parameters at the end of an argument list can be ignored. Unspecified parameters in the middle of an argument list must be accounted for by commas. For example, the following keyword has four parameters-the first and third are used, and the second and fourth are left unspecified:
SAMPLE.INST var_1,,"test"String and numeric input parameters can be constant values (3.32, "part_1", etc.) or any legitimate variable name (see Chapter 1 of the V+ Language User's Guide for the requirements of a variable name). The data type of the constant or variable must agree with the type expected by the keyword. String variables must be preceded by a "$". Precision-point variables must be preceded by a "#". Belt variables must be preceded by a "%". String constants must be enclosed in quotes. Real and integer constants can be used without modification. (V+ keywords cannot be used as variable names-see Appendix A of the V+ Language Reference Guide for a quick-reference list of keywords.)
This section describes the function of the keyword in detail.
Examples of correctly formed instruction lines are presented in this section.
Additional keywords that are similar or are frequently used in conjunction with this instruction are listed here.
|
Please submit comments to: techpubs@adept.com |