Ger Hobbelt

Verified: still a bug. Jison doesn't cope well with epsilon rules which have different FOLLOW sets: these are merged into a single state while they shouldn't.

related: #320

@NightRa : nice catch, this one! Since you seem interested in maximum performance jison parsers, you may be interested in https://github.com/GerHobbelt/jison/commit/d2f8af7886ebda016b1e975fe94414b4134f6d5d (with some more performance-related work done in https://github.com/GerHobbelt/jison/commit/e44add313edf572f0c4f35f4862c08ab7aee41c8 )....

AFAICT this is a 'problem' in the 'vanilla' lexer, which **requires** double-quotes around literal parts of a lexer rule regex, i.e. ``` FS ("f"|"F"|"l"|"L") IS ("u"|"U"|"l"|"L")* ``` should work. The...

See also #67: given the way that the Jison lexer works, `/^/` represents the start of the _rest of the input which still needs to be lexed_. `%options flex` doesn't...

Yes, it is. This is the same problem as #205. Looking into it. On Feb 1, 2017 9:50 PM, "Chizhong Jin" wrote: Hi friend, Thank you for your awesome project....

Provisionally fixed in the https://github.com/GerHobbelt/jison fork in the next build. (Have to nail #343 before this build/release will be available!) See commits: - SHA-1: 7670e5ff34ebc122858cb7717557dac5ede44957 * fixing the correct set...

You might want to check out my fork for this: https://github.com/GerHobbelt/jison/blob/master/lib/jison.js#L1699

The bison advice is applicable to jison grammars as well; however do note that this particular grammar would need more than a %prec hack to make it obvious again what...

The %prec hack is shown in here: https://github.com/GerHobbelt/jison/blob/master/examples/issue-293.jison The trick with %prec is to remember that precedence is a relative thing. In other words: _it takes two (or many) to...