- Update docu

diff --git a/htdocs/manual.html b/htdocs/manual.html
index 10af793237a54085947cbb8dceb6d2c89ee4d2c6..b500083ba8f1589e7cac1533256fe4e001b1739c 100755 (executable)
--- a/htdocs/manual.html
+++ b/htdocs/manual.html
@@ -377,10 +377,11 @@ example above.</p>
 (and provide a rule for matching it): <b>re2c</b> does not provide an
 &lt;&lt;EOF&gt;&gt; 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.</p>
+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.</p>
 <p><b>re2c</b> does not provide start conditions: use a separate scanner
 specification for each start condition (as illustrated in the above example).
 <a name="lbAL" id="lbAL"> </a></p>

diff --git a/re2c.1.in b/re2c.1.in
index 5290d05844dec000f2b49b243811c3d4451015f2..4a7b80ee0b8b06d7487e82db54c3ffc03ede0f9c 100644 (file)
--- 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<<EOF>>\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).