Joe Hildebrand
Joe Hildebrand
I want to leave the ticket open, since it's an interesting problem. We'll just move it's priority down since you're up and running.
@roper79 can you try your use case on [Peggy](https://github.com/peggyjs/peggy/) please? If it's still an issue there, we'll fast-track a fix if possible.
Aren't you missing at least one `)` in there? It'd be easier to see if you split `args` into a separate rule.
This might be a good place for a `& {predicate}` block. Parse a token with something like `$[a-z_]i+`, then check it in a list of valid tokens in the predicate....
Yes, the docs are a little unclear about this, but it's supported behavior. I'll create a bug on peggyjs/peggy to improve the docs.
Since this is documented, can we close this?
How well would this work with just a `report` function, so we don't have to add more syntax?
Two example usages: - In the upcoming peggy-test project: https://github.com/hildjj/peggy-test/blob/891e721093867145b681205fe606a93dbac1e5ce/lib/index.js#L120 - In the upcoming peggy-tag project: https://github.com/hildjj/peggy-tag/blob/bb0f8a1bb778c3e31a6a62ea35e1a052fce84ac1/lib/index.js#L25
> I was just thinking, to better understand project structure, it would be nice to have graphical representation of its component parts with a simple block scheme or something like...
Do you want to use it on the web, or in node? All of the build steps take `lib/**/*.js` and transform and minify them, with the entry point being `lib/peg.js`....