|
|
In general, FMLI does not generate messages on syntax errors.
However, some of the built-in functions, such as
fmlgrep
and
fmlcut
,
and the if-then-else
statement generate their own syntax error messages.
Developers should be aware that the absence of an error message
does not necessarily mean that there is not a syntax error in
their code.
When creating a new menu, form, or text frame, all quotes and backquotes must match. Nuoting mismatches may cause unpredictable results; the frame may never appear, or appear incorrectly.
Prior to FMLI Release 4.0, only the ``$'' notation existed for variable evaluation, and that notation exhibited the behavior now defined for $!. For previously written FMLI applications now being run under FMLI Release 4.0 or 4.0+, a Boolean descriptor, use_incorrect_pre4.0_behavior, can be set in the initialization file, which causes FMLI to ignore the $! notation and interpret $ in the way defined above for $!. The default value (if not defined in the initialization file) for this descriptor is FALSE.