pigeon
pigeon copied to clipboard
mna
Command pigeon generates parsers in Go from a PEG grammar.
It looks like there is not much happening going on in this project. Is this project still active? What are the plans?
Dealing with interfaces can be quite burdensome. Why not add type safety to the project? The data matched by a single character matcher type `byte`, and if you are matching...
This is a nuisance when used, eg, with emacs compilation mode. lex/yacc/byacc/bison/et all use line number preprocessor lines in the generated output to refer back to the original source file...
Hello, First, thanks a lot for maintaining this project, it's a great library! I'm currently using it in https://github.com/bytesparadise/libasciidoc and it's working really well 🙌 However, since https://github.com/mna/pigeon/commit/9fec3898cef80afe60fbe5df398fceca513566b8 was merged,...
The following grammar results in build failure, if generated with `--optimize-grammar`. The same grammar builds with out problem, if the option is not set. Minimal example: ``` X ← z:Z...
eg: ``` { //------ start package main func main() { if len(os.Args) != 2 { log.Fatal("Usage: calculator 'EXPR'") } got, err := ParseReader("", strings.NewReader(os.Args[1])) if err != nil { log.Fatal(err)...
``` { //------ start package main type CompExpr struct { left string op string right string } type LogicExpr struct { left interface{} op string right interface{} } func main()...
Hello! First of all, thank you very much for maintaining this project! I'm hoping that someone can provide a bit of guidance. I apologize in advance for not having a...
Sometimes with really large grammars (such as the wikitext/parsoid peg definitions) it's really hard to debug which rules are actually being used to output the final result. It'd be really...
