Next: Limitations, Previous: Serialized Tables, Up: Top [Contents][Index]
The following is a list of flex
diagnostic messages:
[a-z]+ got_identifier(); foo got_foo();
Using REJECT
in a scanner suppresses this warning.
reject_used_but_not_detected undefined
or
yymore_used_but_not_detected undefined
. These errors can occur
at compile time. They indicate that the scanner uses REJECT
or
yymore()
but that flex
failed to notice the fact, meaning
that flex
scanned the first two sections looking for occurrences
of these actions and failed to find any, but somehow you snuck some in
(via a #include file, for example). Use %option reject
or
%option yymore
to indicate to flex
that you really do use
these features.
%array
and one of its rules matched a string longer than the YYLMAX
constant (8K bytes by default). You can increase the value by
#define’ing YYLMAX
in the definitions section of your flex
input.
unput()
to push
back so much text that the scanner’s buffer could not hold both the
pushed-back text and the current token in yytext
. Ideally the
scanner should dynamically resize the buffer in this case, but at
present it does not.
REJECT
.
yyrestart( yyin );
or, as noted above, switch to using the C++ scanner class.
Next: Limitations, Previous: Serialized Tables, Up: Top [Contents][Index]