Closed conartist6 closed 1 year ago
For reference this is the madness I'm talking about: https://hackernoon.com/the-madness-of-parsing-real-world-javascript-regexps-d9ee336df983#.2l8qu3l76
Right now regexpp is handling it all for us, but I really don't want to bring that kind of syntax weirdness forward into a higher-levels of my streaming parser design. Compatibility brings me little benefit.
My resolution to this issue is not to touch this module, but instead to fork it in the bablr org. Each organization has different needs, history, conventions, and audience.
I'm proposing to remove Annex B parsing from this engine's rules. Because I'm also allowing an AST to be passed as an argument to
parse
it should still be possible to evaluate expressions parsed according to Annex B rules, you'd just have to add your own dependency onregexpp
.Some of that Annex B stuff is madness, most specifically being able to parse expressions with invalid escape codes!