Add anti-LPeg rationale
This commit is contained in:
parent
17fe400e8c
commit
e5e6533401
|
@ -14,3 +14,11 @@ which is equivalent to:
|
||||||
This syntax sugar is similar to the "methods" syntax sugar ([Lua 5.3 §3.4.10](http://www.lua.org/manual/5.3/manual.html#3.4.10),
|
This syntax sugar is similar to the "methods" syntax sugar ([Lua 5.3 §3.4.10](http://www.lua.org/manual/5.3/manual.html#3.4.10),
|
||||||
[Lua 5.2 §3.4.9](http://www.lua.org/manual/5.2/manual.html#3.4.9), [Lua 5.1 §2.5.8](http://www.lua.org/manual/5.1/manual.html#2.5.8)),
|
[Lua 5.2 §3.4.9](http://www.lua.org/manual/5.2/manual.html#3.4.9), [Lua 5.1 §2.5.8](http://www.lua.org/manual/5.1/manual.html#2.5.8)),
|
||||||
and, indeed, `mytable` is only evaluated once.
|
and, indeed, `mytable` is only evaluated once.
|
||||||
|
|
||||||
|
Why not use LPeg?
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
The use of a custom parsing library boils down to two reasons:
|
||||||
|
|
||||||
|
1. LPeg can't stream or produce partial outputs. This just makes it difficult to use for making a compiler.
|
||||||
|
2. LPeg can't process tables. It's still possible to use LPeg to parse table-based structures, but one must serialize them beforehand, which is... far from ideal, to say the least.
|
||||||
|
|
Loading…
Reference in New Issue