Blanks within statement numbers (or references to
statement numbers) are not suppressed; hence, improper
renumbering will occur.
If mismatched parentheses or quotation marks error occur
in the last line of the program, the line number
indicated in the message will indicate the second last
line. This is not a problem if your last line is an
"END" statement.
Input statements having more than 1272 characters may
cause unexpected results.
If you attempt to format a program containing both line
numbers and sequence numbers, the sequence numbers will
be considered part of each statement and will be
formatted accordingly (i.e. converted, if considered a
statement number, and continued on next line after
folding).
If your program contains FORMAT statements with Hollerith
strings that are given by "H" mask and the
statement has to be folded because of its length,
unpredictable things may happen. We recommend the use of
single or double quotes to delineate character strings.
The statement
READ(01,end=501,err=502)data
is not translated correctly.
Too much is done to comment lines. A semicolon (;) causes
the line to be broken into more than one line. Unmatched
parentheses and quotation marks cause warnings to be
generated.
There should be a FILL option that would determine
whether or not to paste together a statement that is
already spread over more than one line, but such that
some line has fewer than 72 characters. This would be
analogous to the ".fi" and ".nf"
options in TF. The FOLD option should be unlinked from
the FILL option.