*/
num_full_table_rows = numecs + 1;
- /* Unless -a, declare it "short" because it's a real
+ /* Unless -Ca, declare it "short" because it's a real
* long-shot that that won't be large enough.
*/
printf( "static const %s yy_nxt[][%d] =\n {\n",
flexdoc \- documentation for flex, fast lexical analyzer generator
.SH SYNOPSIS
.B flex
-.B [\-abcdfhilnpstvwBFILTV78+ \-C[efFmr] \-Pprefix \-Sskeleton]
+.B [\-bcdfhilnpstvwBFILTV78+ \-C[aefFmr] \-Pprefix \-Sskeleton]
.I [filename ...]
.SH DESCRIPTION
.I flex
.I flex
has the following options:
.TP
-.B \-a
-(``align'') instructs flex to trade off larger tables in the
-generated scanner for faster performance because the elements of
-the tables are better aligned for memory access and computation. On some RISC
-architectures, fetching and manipulating longwords is more efficient than
-with smaller-sized datums such as shortwords. This option can
-double the size of the tables used by your scanner.
-.TP
.B \-b
Generate backing-up information to
.I lex.backup.
scanner class. See the section on Generating C++ Scanners below for
details.
.TP
-.B \-C[efmF]
-controls the degree of table compression.
+.B \-C[aefFmr]
+controls the degree of table compression and, more generally, trade-offs
+between small scanners and fast scanners.
+.IP
+.B \-Ca
+("align") instructs flex to trade off larger tables in the
+generated scanner for faster performance because the elements of
+the tables are better aligned for memory access and computation. On some
+RISC architectures, fetching and manipulating longwords is more efficient
+than with smaller-sized datums such as shortwords. This option can
+double the size of the tables used by your scanner.
.IP
.B \-Ce
directs
-C
-C{f,F}e
-C{f,F}
+ -C{f,F}a
fastest & largest
.fi
for dealing well with large sets of rules. Aside from the effects on
scanner speed of the table compression
.B \-C
-and
-.B \-a
options outlined above,
there are a number of options/actions which degrade performance. These
are, from most expensive to least: