Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Minor typos fixes in the lemon documentation. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
bd1181fb39d9f1f5b78dba8f3bdbd991 |
| User & Date: | drh 2019-07-15 17:48:15 |
Context
|
2019-07-16
| ||
| 13:44 | Updates to the testing document. (check-in: 0d69a8d268 user: drh tags: branch-3.29) | |
|
2019-07-15
| ||
| 19:25 | Update syntax diagrams to show the FILTER clause on aggregate functions. Start a change log for version 3.30.0. (check-in: ba9800704d user: drh tags: trunk) | |
| 17:48 | Minor typos fixes in the lemon documentation. (check-in: bd1181fb39 user: drh tags: trunk) | |
| 17:17 | Fix a missing space in the selfcontained.html webpage. (check-in: 127e0a0347 user: drh tags: trunk) | |
Changes
Changes to pages/lemon.in.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
..
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
<p>Lemon generates an LALR(1) parser. It's operation is similar to the
more familiar tools [https://en.wikipedia.org/wiki/Yacc|Yacc] and
[https://en.wikipedia.org/wiki/GNU_bison|Bison], but Lemon adds important
improvements, including:
<ul>
<li><p>
The grammar syntax is less error prone - using symbol names for
semantic values rather that the "$1"-style positional notation
of Yacc.
<li><p>
In Lemon, the tokenizer calls the parser. Yacc operates the other
way around, with the parser calling the tokenizer. The Lemon
approach is reentrant and threadsafe, whereas Yacc uses global
variables and is therefore neither. Reentrancy is especially
................................................................................
<p>Lemon is also used to generate parse for the query pattern
expressions in the [FTS5] extension. In this case, the input grammar
file is [https://sqlite.org/src/file/ext/fts5/fts5parse.y|fts5parse.y].
<h2>Lemon Customizations Especially For SQLite</h2>
<p>One of the advantages of hosting code generator tool as part of
the project is that the tools can be optimized to serve specific needs of
the overall project. Lemon has benefited from this effect. Over the years,
the Lemon parser generator has been extended and enhanced to provide
new capabilities and improved performance to SQLite. A few of the
specific enhancements to Lemon that are specifically designed for use
by SQLite include:
|
|
|
|
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
..
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
<p>Lemon generates an LALR(1) parser. It's operation is similar to the
more familiar tools [https://en.wikipedia.org/wiki/Yacc|Yacc] and
[https://en.wikipedia.org/wiki/GNU_bison|Bison], but Lemon adds important
improvements, including:
<ul>
<li><p>
The grammar syntax is less error prone - using symbolic names for
semantic values rather that the "$1"-style positional notation
of Yacc.
<li><p>
In Lemon, the tokenizer calls the parser. Yacc operates the other
way around, with the parser calling the tokenizer. The Lemon
approach is reentrant and threadsafe, whereas Yacc uses global
variables and is therefore neither. Reentrancy is especially
................................................................................
<p>Lemon is also used to generate parse for the query pattern
expressions in the [FTS5] extension. In this case, the input grammar
file is [https://sqlite.org/src/file/ext/fts5/fts5parse.y|fts5parse.y].
<h2>Lemon Customizations Especially For SQLite</h2>
<p>One of the advantages of hosting code generator tools as part of
the project is that the tools can be optimized to serve specific needs of
the overall project. Lemon has benefited from this effect. Over the years,
the Lemon parser generator has been extended and enhanced to provide
new capabilities and improved performance to SQLite. A few of the
specific enhancements to Lemon that are specifically designed for use
by SQLite include:
|