You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It all depends on what language you're picking for portability.
Antlr is what I personally used before, and has targets for Java, C#, Python, JavaScript, Go, C++, Swift, and PHP (and the Java target even has ambiguous tree construction!).
Tree-sitter generates a pure C runtime with bindings for Rust, JavaScript (WASM), JavaScript (Node Native Modules), Python, Ruby, and Haskell, and ticks the most boxes of Matklad's Modern Parser Generator goals.
Honestly, you're best off searching for whatever language your using's most popular parsing tools/generators, as most generated and aot-machine-optimized parsing is "fast enough," and ease of use in the target language is important as well.
(Though I'm curious: what platforms are you worried about supporting that you'd need a parser generator for?)
not necessarily portability of the parser. most compilers run on x86 anyway, where rust works fine.
Currently the zz compiler is built in rust for that reason, using pest (feel free to add to the list).
But i'm adding docs and state machine generators now and considering self hosting, depending on what's out there.
we're migrating away from rust for portability, but leaving pest behind is pretty sad because it's just so good!
given you probably researched alot, is there maybe a list of inspirations you had?
The text was updated successfully, but these errors were encountered: