From: helly <helly@642ea486-5414-0410-9d7f-a0204ed87703>
Date: Mon, 26 Feb 2007 09:21:52 +0000 (+0000)
Subject: - Update docu
X-Git-Tag: 0.13.6~222
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=764356aa3addd1747e4ec4e9f8cf32f33c95f535;p=re2c

- Update docu
---

diff --git a/re2c/htdocs/manual.html b/re2c/htdocs/manual.html
index e6fac74b..163f50bc 100755
--- a/re2c/htdocs/manual.html
+++ b/re2c/htdocs/manual.html
@@ -255,7 +255,7 @@ the scanner code should be wrapped inside a loop.</p>
 tweaked using inplace configurations "state:abort" and "state:nextlabel".</p>
 <a name="lbAH" id="lbAH"> </a>
 <h2>SCANNER SPECIFICATIONS</h2>
-<p>Each scanner specification consists of a set of <i>rules</i>, <i>name
+<p>Each scanner specification consists of a set of <i>rules</i>, <i>named
 definitions</i> and <i>configurations</i>.</p>
 <p><i>Rules</i> consist of a regular expression along with a block of C/C++
 code that is to be executed when the associated <i>regular expression</i> is
@@ -267,10 +267,11 @@ matched.</p>
 <dl compact="compact">
 <dd><i>name</i> = <i>regular expression</i>;</dd>
 </dl>
-<p>Configurations look like name definitions whose names start with
+<p>Configurations look like named definitions whose names start with
 "<b>re2c:</b>":</p>
 <dl compact="compact">
 <dd>re2c:<i>name</i> = <i>value</i>;</dd>
+<dd>re2c:<i>name</i> = <b>"</b><i>value</i><b>"</b>;</dd>
 </dl>
 <a name="lbAI" id="lbAI"> </a>
 <h2>SUMMARY OF RE2C REGULAR EXPRESSIONS</h2>
@@ -471,7 +472,7 @@ specification for each start condition (as illustrated in the above example).
 <h2>SEE ALSO</h2>
 <p>flex(1), lex(1). More information on <b>re2c</b> can be found here:
 <b><a href=
-"http://sourceforge.net/projects/re2c/">http://sourceforge.net/projects/re2c/</a></b></p>
+"http://re2c.org/">http://re2c.org/</a></b></p>
 <a name="lbAN" id="lbAN"> </a>
 <h2>AUTHORS</h2>
 <ul>
diff --git a/re2c/re2c.1.in b/re2c/re2c.1.in
index a718ef3a..09cd5108 100644
--- a/re2c/re2c.1.in
+++ b/re2c/re2c.1.in
@@ -292,7 +292,7 @@ Please see examples/push.re for push-model scanner. The generated code can be
 tweaked using inplace configurations "\fBstate:abort\fP" and "\fBstate:nextlabel\fP".
 
 .SH "SCANNER SPECIFICATIONS"
-Each scanner specification consists of a set of \fIrules\fP, \fIname
+Each scanner specification consists of a set of \fIrules\fP, \fInamed
 definitions\fP and \fIconfigurations\fP.
 .LP
 \fIRules\fP consist of a regular expression along with a block of C/C++ code that
@@ -308,12 +308,15 @@ Named definitions are of the form:
 \fIname\fP \fC=\fP \fIregular expression\fP\fC;\fP
 .RE
 .LP
-Configurations look like name definitions whose names start 
+Configurations look like named definitions whose names start 
 with "\fBre2c:\fP":
 .P
 .RS
 \fCre2c:\fP\fIname\fP \fC=\fP \fIvalue\fP\fC;\fP
 .RE
+.RS
+\fCre2c:\fP\fIname\fP \fC=\fP \fB"\fP\fIvalue\fP\fB"\fP\fC;\fP
+.RE
 
 .SH "SUMMARY OF RE2C REGULAR EXPRESSIONS"
 .TP
@@ -570,7 +573,7 @@ flex(1), lex(1).
 More information on \*(re can be found here:
 .PD 0
 .P
-.B http://sourceforge.net/projects/re2c/
+.B http://re2c.org/
 .PD 1
 
 .SH AUTHORS