Glen Huang
Glen Huang
just a side note: `"export-var": "var parser"` looks somewhat awkward. Maybe pegjs could automatically add `var` to it if there is no dot inside the variable name?
actually, this is a rather different beast. authors might do `"export-var": "var parser = module.exports"`, in which case it should probably be `"export-var": ["parser", "module.exports"]`. maybe I should open a...
or overloading `options`: ``` { // intializer // pegjs will respect these options.exportVar = ["parser", "module.exports"] options.allowedStartRules = ["start", "non-start"] } ``` but this probably means options specified in CLI...
> You have such a use case? If so, can you describe it? If the language allows including another files, you might want to load the file and recursively call...
And the issue regarding `--export-var`: #140
Just my two cents: ### Special syntax This syntax should also be able to distinguish lists allowing two or more items. It's a pretty common pattern that when the list...
> It seems that your first two bullet points both stem from the idea that modularity and abstraction somehow makes things harder to read or understand. no, that's not what...
It seems you are talking about a totally different feature. The syntax proposed by David is to use the parameters in the grammar part, and as I said, it simply...
@dmajda, I'm thinking of another syntax to solve the merging problem, which behaves much like the `$ expression` syntax. The `$ expression` syntax returns the matched string, no matter how...