diff options
Diffstat (limited to 'doc/lemon.html')
| -rw-r--r-- | doc/lemon.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/lemon.html b/doc/lemon.html index 056ae5f5b..17988deef 100644 --- a/doc/lemon.html +++ b/doc/lemon.html @@ -123,7 +123,7 @@ Suppress generation of the report file. <li><b>-r</b> Do not sort or renumber the parser states as part of optimization. <li><b>-s</b> -Show parser statistics before existing. +Show parser statistics before exiting. <li><b>-T<i>file</i></b> Use <i>file</i> as the template for the generated C-code parser implementation. <li><b>-x</b> @@ -488,7 +488,7 @@ is an error.</p> The precedence of a grammar rule is equal to the precedence of the left-most terminal symbol in the rule for which a precedence is defined. This is normally what you want, but in those cases where -you want to precedence of a grammar rule to be something different, +you want the precedence of a grammar rule to be something different, you can specify an alternative precedence symbol by putting the symbol in square braces after the period at the end of the rule and before any C-code. For example:</p> @@ -689,7 +689,7 @@ on Parse(). <a name='extractx'></a> <h4>The <tt>%extra_context</tt> directive</h4> -The <tt>%extra_context</tt> directive instructs Lemon to add a 2th parameter +The <tt>%extra_context</tt> directive instructs Lemon to add a 2nd parameter to the parameter list of the ParseAlloc() and ParseInif() functions. Lemon doesn't do anything itself with these extra argument, but it does store the value make it available to C-code action routines, destructors, @@ -699,9 +699,9 @@ and so forth. For example, if the grammar file contains:</p> %extra_context { MyStruct *pAbc } </pre></p> -<p>Then the ParseAlloc() and ParseInit() functions will have an 2th parameter +<p>Then the ParseAlloc() and ParseInit() functions will have an 2nd parameter of type "MyStruct*" and all action routines will have access to -a variable named "pAbc" that is the value of that 2th parameter.</p> +a variable named "pAbc" that is the value of that 2nd parameter.</p> <p>The <tt>%extra_argument</tt> directive works the same except that it is passed in on the Parse() routine instead of on ParseAlloc()/ParseInit(). @@ -996,7 +996,7 @@ on the parser's stack associated with terminal and non-terminal symbols. The values of all terminal symbols must be of the same type. This turns out to be the same data type as the 3rd parameter to the Parse() function generated by Lemon. Typically, you will -make the value of a terminal symbol by a pointer to some kind of +make the value of a terminal symbol be a pointer to some kind of token structure. Like this:</p> <p><pre> |