Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jison doesn't handle indirect left recursion properly #1

Closed
GerHobbelt opened this issue Jul 7, 2016 · 2 comments
Closed

jison doesn't handle indirect left recursion properly #1

GerHobbelt opened this issue Jul 7, 2016 · 2 comments

Comments

@GerHobbelt
Copy link
Owner

Don't know yet if this is particular to my fork or the original already.

Ran into this issue when working on lex-parser: commits follow

GerHobbelt added a commit to GerHobbelt/lex-parser that referenced this issue Jul 7, 2016
@GerHobbelt
Copy link
Owner Author

GerHobbelt commented Jul 7, 2016

@GerHobbelt
Copy link
Owner Author

Whoops. Don't understand I could have overlooked these! 👎 👎

Conflict in grammar: multiple actions possible when lookahead token is NAME in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)
Conflict in grammar: multiple actions possible when lookahead token is START_INC in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)
Conflict in grammar: multiple actions possible when lookahead token is START_EXC in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)
Conflict in grammar: multiple actions possible when lookahead token is { in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)
Conflict in grammar: multiple actions possible when lookahead token is ACTION in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)
Conflict in grammar: multiple actions possible when lookahead token is INCLUDE in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)
Conflict in grammar: multiple actions possible when lookahead token is OPTIONS in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)
Conflict in grammar: multiple actions possible when lookahead token is UNKNOWN_DECL in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)
Conflict in grammar: multiple actions possible when lookahead token is %% in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)
Conflict in grammar: multiple actions possible when lookahead token is | in state 18
- reduce by rule: regex_list -> nonempty_regex_list
- reduce by rule: regex -> nonempty_regex_list
  (Resolved R/R conflict: use first production declared in grammar.)

GerHobbelt added a commit to GerHobbelt/lex-parser that referenced this issue Jul 8, 2016
…of conflicts which I didn't spot -- regenerated parser
GerHobbelt added a commit that referenced this issue Jul 8, 2016
GerHobbelt added a commit that referenced this issue Sep 9, 2016
  showing slightly more content to help users locate and fix the issue at
  hand.

- augmented the optionally included `main` function to report the parse
  result type and value + returns the parser result when this is a numeric
  or boolean value: this helps simplify the construction of small tools,
  which use a jison grammar at their core: now you can return the CLI exit
  value directly in your grammar actions as these numbers will be passed
  to `process.exit()`

- refactored the expansion of the `$1`, `@1` and `#1` macros in grammar
  actions.

- added the ability to obtain the related 'stack index' for a grammar term
  by the macro `\`1` / `\`name`: this helps us writing grammars (grammar
  actions!) which maintain additional parser stacks next to the ones
  maintained by jison (stack, vstack, lstack).
GerHobbelt pushed a commit that referenced this issue Nov 11, 2016
GerHobbelt pushed a commit that referenced this issue Nov 17, 2016
Added support for ES2015 module generation
GerHobbelt pushed a commit that referenced this issue Jan 28, 2017
Add updates from nolanlawson debuggable branch
GerHobbelt pushed a commit that referenced this issue Apr 9, 2017
GerHobbelt pushed a commit that referenced this issue Nov 7, 2020
GerHobbelt pushed a commit that referenced this issue Nov 7, 2020
Fix OS Command Injection on Jison
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

No branches or pull requests

1 participant