Comments (2)
Thanks for the links. I haven't seen that paper yet, and I'm curious how the ALL(*) parsing works. I think that some limited grammar rewriting is possible to avoid trivial left-recursion cases in the same way that pe's "common" optimizations do grammar rewriting, such as transforming patterns like "a" "b"
into "ab"
or "a" / "b"
into [ab]
.
If you continue the section you quoted, they say this:
Direct left-recursion covers the most common cases, such as arithmetic expression productions, like E → E . id, and C declarators. We made an engineering decision not to support indirect or hidden left-recursion.
So they do not handle the more difficult left-recursion cases, which sounds like a practical decision (especially since they are apparently doing grammar analysis at parse time instead of compile time).
from pe.
Not sure how applicable this is to PEG but ANTLR can deal with direct left-recursion very gracefully and from its docs I quote
The most natural expression of some common language constructs is left recursive. For example C declarators and arithmetic expressions.
which is why it's always a very handy feature for a parser generator to support at least direct left recursion.
See also the corresponding publication. From there I quote
ANTLR 4 generates ALL(*) parsers and supports direct left-recursion through grammar rewriting
so maybe a similar automatic grammar-rewriting strategy could be used by pe
as well?
from pe.
Related Issues (20)
- Remove packrat parser
- Captured choices not working with Cython machine parser
- Character classes in machine parser fail at odd times
- Inefficiencies in regex optimization
- More "common" optimizations HOT 1
- Separate error type for failing to parse a grammar
- Change implicit optional types to explicit HOT 1
- Update Python versions HOT 1
- Make implicit Optionals into explicit for current Mypy HOT 1
- Add common patterns in code
- Bug: Newlines make the debug output difficult to read. HOT 1
- Add python version to publishing action
- Update to Cython 3.0
- Lint with ruff instead of flake8
- Multiple repeat operators HOT 4
- Difference with machine/packrat parsers and captures HOT 1
- (Helpful) Error messages HOT 3
- Common optimization misbehaving on character classes HOT 1
- "Sidecar" objects for accumulative parsing
- Bounded repetitions
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pe.