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

named references test failures #4

Closed
zaach opened this issue Aug 12, 2013 · 5 comments
Closed

named references test failures #4

zaach opened this issue Aug 12, 2013 · 5 comments

Comments

@zaach
Copy link
Owner

zaach commented Aug 12, 2013

Hey @cdibbs, I'm getting tests failures on the new feature. Were these passing for you? Are you using jison 0.4.10?

    test named group ()
      ⚡ Error: Parse error on line 1:
      one, two
      ^
      Expecting 'word[alice]', got 'word'
          at typal_constructor.parseError (/Users/zcarter/repos/ebnf-parser/node_modules/jison/lib/jison.js:1185:15)
          at typal_constructor.parse (/Users/zcarter/repos/ebnf-parser/node_modules/jison/lib/jison.js:1301:22)
          at /Users/zcarter/repos/ebnf-parser/tests/ebnf.js:62:39
          at test (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:29:20)
          at next (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:69:7)
          at Object.end (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:25:7)
          at test (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:41:28)
          at next (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:69:7)
          at Object.end (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:25:7)
          at test (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:41:28)
    test named option (?)
      ⚡ Error: Parse error on line 1:
      oneor two
      ^
      Expecting 'word[alex]', got 'word'
          at typal_constructor.parseError (/Users/zcarter/repos/ebnf-parser/node_modules/jison/lib/jison.js:1185:15)
          at typal_constructor.parse (/Users/zcarter/repos/ebnf-parser/node_modules/jison/lib/jison.js:1301:22)
          at /Users/zcarter/repos/ebnf-parser/tests/ebnf.js:62:39
          at test (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:29:20)
          at next (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:69:7)
          at Object.end (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:25:7)
          at test (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:46:14)
          at next (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:69:7)
          at Object.end (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:25:7)
          at test (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:41:28)
    test named complex expression (())
      ⚡ Error: Parse error on line 1:
      one two three four, 
      ^
      Expecting 'word[alpha]', got 'word'
          at typal_constructor.parseError (/Users/zcarter/repos/ebnf-parser/node_modules/jison/lib/jison.js:1185:15)
          at typal_constructor.parse (/Users/zcarter/repos/ebnf-parser/node_modules/jison/lib/jison.js:1301:22)
          at /Users/zcarter/repos/ebnf-parser/tests/ebnf.js:62:39
          at test (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:29:20)
          at next (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:69:7)
          at Object.end (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:25:7)
          at test (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:46:14)
          at next (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:69:7)
          at Object.end (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:25:7)
          at test (/Users/zcarter/repos/ebnf-parser/node_modules/test/test.js:46:14)
@cdibbs
Copy link
Contributor

cdibbs commented Aug 12, 2013

Yes, these were all passing. The mods to ebnf-parser require the changes in jison. I just pulled down two fresh copies to be sure. Here is the other pull request: zaach/jison#181. Note that I (believe I) fixed the speed issues in the token stack enhancement, too, but we can get rid of that if it hinders the named references enhancement.

@zaach
Copy link
Owner Author

zaach commented Aug 18, 2013

@cdibbs Yes, could we decouple the PRs? I intend to make the token stack optional either way, like other parser features.

@cdibbs
Copy link
Contributor

cdibbs commented Aug 18, 2013

@zaach Sorry about that. I'm still pretty new to git/github. I can work on making the token stack optional as I find time, later.

@cdibbs
Copy link
Contributor

cdibbs commented Sep 1, 2013

@zaach Thought I'd check in on this - were you ever able to get this working? zaach/jison#185 decouples the PRs. I looked over what I was doing, and the biggest gotcha was that I temporarily sym-linked the updated Jison module into the ebnf-parser node_modules directory before rebuilding ebnf-parser (not sure whether there's a better way to do this). Without the Jison changes at the BNF level, the EBNF stuff cannot work.

@zaach
Copy link
Owner Author

zaach commented Sep 1, 2013

Oh, I didn't notice the new PR. I'll test it out locally – thanks!

@zaach zaach closed this as completed Sep 8, 2013
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

2 participants