Skip to content

Conversation

@GerHobbelt
Copy link
Contributor

@GerHobbelt GerHobbelt commented Jan 31, 2017

…r by also listing the entire line containing the offending character(s).
… showing slightly more context around any failure location in order to aid the user to locate and fix the issue in the source file(s).

- bumped build revision
…h to prevent npm3 from attempting to installing the (unused) submodules there
…and hid platform-specific trouble with the regex /u flag (not support in older NodeJS)

  + fix: use XRegExp in lexer to enable Unicode keyword support on all platforms

- replaced `JSON.parse` with `eval` which is safe to use here and supports octal escapes; any eval failures are caught using try/catch and flagged as non-keyword, which is safe behaviour.

- bumped build revision
…heck if a user-specified lexer rule is eligible for `easy_keyword_rules` processing mode.
…xer generator. (Aparently nobody ever used jison ES6 output mode as there were a few fatal API problems in there too. These have been fixed provisionally) The generated code is `import`-patched in a rather hacky way as jison doesn't yet correctly support the desirable `%code imports %{...%}` feature...
…e 'external dependencies' ARE NOT included in the rollup but kept external. ==> jison-helpers-lib MUST NOT be included in the dist/ rollup library files for lex-parser!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants