Shahar Soel

I am closing the PR for now with the hope that in ~7 months when nodejs 14 reaches EOL we can provide an ESM only package, perhaps even without a...

Initiated due to discussion in: https://github.com/SAP/chevrotain/issues/645

If it is a syntax error it needs to throw and the Parser will auto recover if errorRecovery is enabled, That is what happens for example in MisMatchTokenError - https://github.com/SAP/chevrotain/blob/master/packages/chevrotain/src/parse/parser/traits/recognizer_engine.ts#L936-L938...

This is up for grabs, generating a simple EBNF text should be simple as the grammar structure is already well defined. Making it pretty with advanced features may be more...

Have a look at the playground: - https://sap.github.io/chevrotain/playground/ Hover on the syntax diagrams and see what lights up. Also try to click on terminals/non-terminals and see that it navigates to...

This looks good. - We can go for MVP as the first step. - I am not sure how we should represent the terminals, e.g: "(?:""|[^"])*" vs /(?:""|[^"])*/ - Maybe...

What if we have a regExp: ```javascript /foo|bar/ ``` and we also have NonTerminals called "foo" and "bar". Won't it create ambiguius EBNF? ``` // Is this a Non-Terminal with...

EcmaScript regExps also have constructs that do not exist in EBNF or worse yet may mean different things in EBNF. e.g in EBNF: `B{2}` is a repetition of the 2...

> Would you prefer that I switch to the ISO-14977 style? No, I think the W3C style is easier to understand as well. > maybe add an argument that allows...

### Background to some of this issue The root evil is that we are re-processing the text when calculating the column/line info. It does not matter if we do this...