From: helly Date: Sun, 22 Apr 2007 20:03:08 +0000 (+0000) Subject: - Fix docu X-Git-Tag: 0.13.6~183 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=229f364165178b03274c333586b08f5e7a23ca79;p=re2c - Fix docu --- diff --git a/re2c/htdocs/manual.html b/re2c/htdocs/manual.html index fa04370d..48961502 100755 --- a/re2c/htdocs/manual.html +++ b/re2c/htdocs/manual.html @@ -81,7 +81,7 @@ will receive. If -1 is in effect then YYMAXFILL can be triggered once after the last /*!re2c */.

You can also use /*!ignore:re2c */ blocks that allows to document the scanner code and will not be part of the output.

- + 

OPTIONS

re2c provides the following options:

@@ -144,7 +144,7 @@ version.



- + 

INTERFACE CODE

Unlike other scanner generators, re2c does not generate complete scanners: the user must supply some interface code. In particular, the user @@ -219,7 +219,7 @@ disabled.



- + 

SCANNER WITH STORABLE STATES

When the -f flag is specified, re2c generates a scanner that can store its current state, return to the caller, and later resume operations @@ -266,7 +266,7 @@ placing a "/*!getstate:re2c */" comment. This is especially useful when the scanner code should be wrapped inside a loop.

Please see examples/push.re for push-model scanner. The generated code can be tweaked using inplace configurations "state:abort" and "state:nextlabel".

- + 

SCANNER WITH CONDITION SUPPORT

You can preceed regular-expressions with a list of condition names when using the -c @@ -280,7 +280,7 @@ provide a code block that does not have a scanner part. Meaning it does not allow any regular expression. The condition value referring to this special block is always the one with the enumeration value 0.

- + 

SCANNER SPECIFICATIONS

Each scanner specification consists of a set of rules, named definitions and configurations.

@@ -311,7 +311,7 @@ name at all. In the latter case the rule cannot have a regular expression.
re2c:name = value;
re2c:name = "value";
- + 

SUMMARY OF RE2C REGULAR EXPRESSIONS

"foo"
@@ -379,7 +379,7 @@ the only portable "any" rules are (.|"\n") and [^].

The regular expressions listed above are grouped according to precedence, from highest precedence at the top to lowest at the bottom. Those grouped together have equal precedence.

- + 

INPLACE CONFIGURATION

It is possible to configure code generation inside re2c blocks. The following lists the available configurations:

@@ -487,12 +487,12 @@ generate a static jump table for conditions.
re2c:variable:yytarget = yytarget ;
Allows to overwrite the name of the variable yytarget.
- + 

UNDERSTANDING RE2C

The subdirectory lessons of the re2c distribution contains a few step by step lessons to get you started with re2c. All examples in the lessons subdirectory can be compiled and actually work.

- + 

FEATURES

re2c does not provide a default action: the generated code assumes that the input will consist of a sequence of tokens. Typically this can be @@ -508,17 +508,17 @@ to see if it is the sentinel and act accordingly. And you can also use YYFILL(n) 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). -

+specification for each start condition (as illustrated in the above example).

+ 

BUGS

Difference only works for character sets.

The re2c internal algorithms need documentation.

- + 

SEE ALSO

flex(1), lex(1). More information on re2c can be found here: http://re2c.org/

- + 

AUTHORS