The following features are available to increase the readability of a WFL code:
-
Free formatting
-
Case-insensitivity
-
Comments
-
Subroutine ending identifiers
Free formatting enables WFL constructs to be entered in any column of a line and continue over any number of lines. You can use varying amounts of indentation to indicate the nesting of constructs. However, the invalid character must appear in the first column.
WFL is case-insensitive. Keywords and variables can be in uppercase, lowercase, or mixed case. However, if the CASESENSITIVEPW security option is set, passwords are treated in a case-sensitive manner; lowercase characters are not converted to uppercase, and some special characters can be included without enclosing the token in double quotes. The following special characters are accepted in such a password.
& |
- |
{ |
} |
\ |
~ |
` |
[ |
] |
| |
: |
$ |
< |
* |
@ |
( |
_ |
+ |
> |
= |
! |
^ |
? |
# |
The pound sign (#) cannot be the first character of the password, and the ampersand (&) cannot be used when the password is used in a WRAP or UNWRAP statement unless the password is enclosed in double quotes.
A percent sign (%) can appear in any column of a line, and will cause the WFL compiler to ignore the remainder of the line, which can be used for comments.
The identifier that identifies a subroutine can be repeated after the END statement for that subroutine. In cases where subroutines are nested, this feature helps eliminate confusion about which subroutine is being ended.
Example
The following example illustrates the use of a nested subroutine ending identifier:
SUBROUTINE SUBOUTER; % Beginning of outer subroutine BEGIN SUBROUTINE SUBNESTED; % Beginning of nested subroutine BEGIN . . END SUBNESTED; % End of nested subroutine . . END SUBOUTER; % End of outer subroutine