%option backup
’-CF
is used, the generated scanner will run faster (see the ‘--perf-report’ flag).
Only users who wish to squeeze every last cycle out of their scanners
need worry about this option. (see Performance).
%option debug
’yy_flex_debug
is non-zero
(which is the default), the scanner will write to stderr a line
of the form:
-accepting rule at line 53 ("the matched text")
The line number refers to the location of the rule in the file defining the scanner (i.e., the file that was fed to flex). Messages are also generated when the scanner backs up, accepts the default rule, reaches the end of its input buffer (or encounters a NUL; at this point, the two look the same as far as the scanner's concerned), or reaches an end-of-file.
%option perf-report
’flex
input file which will
cause a serious loss of performance in the resulting scanner. If you
give the flag twice, you will also get comments regarding features that
lead to minor performance losses.
Note that the use of REJECT
, and
variable trailing context (see Limitations) entails a substantial
performance penalty; use of yymore()
, the ‘^’ operator, and
the ‘--interactive’ flag entail minor performance penalties.
%option nodefault
’%option trace
’flex
run in trace mode. It will generate a lot of
messages to stderr concerning the form of the input and the
resultant non-deterministic and deterministic finite automata. This
option is mostly for use in maintaining flex
.
%option nowarn
’%option verbose
’flex
should write to stderr a summary of
statistics regarding the scanner it generates. Most of the statistics
are meaningless to the casual flex
user, but the first line
identifies the version of flex
(same as reported by ‘--version’),
and the next line the flags used when generating the scanner, including
those that are on by default.
%option warn
’