From ea4c86119de3ed3c6e2fabf0a3a4e672e6ce39ec Mon Sep 17 00:00:00 2001 From: helly Date: Sat, 15 Apr 2006 17:06:11 +0000 Subject: [PATCH] - Update docu --- htdocs/manual.html | 9 +++++---- re2c.1.in | 12 ++++++++---- 2 files changed, 13 insertions(+), 8 deletions(-) diff --git a/htdocs/manual.html b/htdocs/manual.html index 10af7932..b500083b 100755 --- a/htdocs/manual.html +++ b/htdocs/manual.html @@ -377,10 +377,11 @@ example above.

(and provide a rule for matching it): re2c does not provide an <<EOF>> expression. If the source is from a null-byte terminated string, a rule matching a null character will suffice. If the source is from a -file then the approach taken in the example can be used: pad the input with a -newline (or some other character that can't appear within another token); upon -recognizing such a character check to see if it is the sentinel and act -accordingly.

+file then you could pad the input with a newline (or some other character that +cannot appear within another token); upon recognizing such a character check +to see if it is the sentinel and act accordingly. And you can also use YYFILL +to end the scanner in case not enough characters are available which is nothing +else then e detection of end of data/file.

re2c does not provide start conditions: use a separate scanner specification for each start condition (as illustrated in the above example).

diff --git a/re2c.1.in b/re2c.1.in index 5290d058..4a7b80ee 100644 --- a/re2c.1.in +++ b/re2c.1.in @@ -7,6 +7,9 @@ .ds rx regular expression .ds lx \fIl\fP-expression \"$Log$ +\"Revision 1.52 2006/04/15 17:06:10 helly +\"- Update docu +\" \"Revision 1.51 2006/04/15 16:27:28 helly \"- Fix heading \" @@ -617,10 +620,11 @@ The user must arrange for a sentinel token to appear at the end of input \*(re does not provide an \fC<>\fP expression. If the source is from a null-byte terminated string, a rule matching a null character will suffice. If the source is from a -file then the approach taken in the example can be used: pad the input with -a newline (or some other character that can't appear within another token); -upon recognizing such a character check to see if it is the sentinel -and act accordingly. +file then you could pad the input with a newline (or some other character that +cannot appear within another token); upon recognizing such a character check +to see if it is the sentinel and act accordingly. And you can also use YYFILL +to end the scanner in case not enough characters are available which is nothing +else then e detection of end of data/file. .LP \*(re does not provide start conditions: use a separate scanner specification for each start condition (as illustrated in the above example). -- 2.40.0