summaryrefslogtreecommitdiffstats
path: root/usr.bin/lex
diff options
context:
space:
mode:
authorschweikh <schweikh@FreeBSD.org>2003-01-01 18:49:04 +0000
committerschweikh <schweikh@FreeBSD.org>2003-01-01 18:49:04 +0000
commitd3367c5f5d3ddcc6824d8f41c4cf179f9a5588f8 (patch)
treef412dafc7d29429919e8770cdefeb37441fc1299 /usr.bin/lex
parent718a7892bc6da2237db71c255051dd54a4e93a92 (diff)
downloadFreeBSD-src-d3367c5f5d3ddcc6824d8f41c4cf179f9a5588f8.zip
FreeBSD-src-d3367c5f5d3ddcc6824d8f41c4cf179f9a5588f8.tar.gz
Correct typos, mostly s/ a / an / where appropriate. Some whitespace cleanup,
especially in troff files.
Diffstat (limited to 'usr.bin/lex')
-rw-r--r--usr.bin/lex/flexdef.h2
-rw-r--r--usr.bin/lex/lex.12
2 files changed, 2 insertions, 2 deletions
diff --git a/usr.bin/lex/flexdef.h b/usr.bin/lex/flexdef.h
index 6fc168c..03651ea 100644
--- a/usr.bin/lex/flexdef.h
+++ b/usr.bin/lex/flexdef.h
@@ -368,7 +368,7 @@ extern struct hash_entry *ccltab[CCL_HASH_SIZE];
* use_read - if true (-f, -F, or -Cr) then use read() for scanner input;
* otherwise, use fread().
* yytext_is_array - if true (i.e., %array directive), then declare
- * yytext as a array instead of a character pointer. Nice and inefficient.
+ * yytext as an array instead of a character pointer. Nice and inefficient.
* do_yywrap - do yywrap() processing on EOF. If false, EOF treated as
* "no more files".
* csize - size of character set for the scanner we're generating;
diff --git a/usr.bin/lex/lex.1 b/usr.bin/lex/lex.1
index dcfc827..918039b 100644
--- a/usr.bin/lex/lex.1
+++ b/usr.bin/lex/lex.1
@@ -3132,7 +3132,7 @@ can't figure this out, and it will plan for possibly needing to back up
when it has scanned a token like "auto" and then the next character
is something other than a newline or a letter. Previously it would
then just match the "auto" rule and be done, but now it has no "auto"
-rule, only a "auto\\n" rule. To eliminate the possibility of backing up,
+rule, only an "auto\\n" rule. To eliminate the possibility of backing up,
we could either duplicate all rules but without final newlines, or,
since we never expect to encounter such an input and therefore don't
how it's classified, we can introduce one more catch-all rule, this
OpenPOWER on IntegriCloud