-
Notifications
You must be signed in to change notification settings - Fork 466
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
lextab.py and yacctab.py #293
Comments
The current Github version of PLY writes no such files. In older versions, there are optional arguments to lex() and yacc() that control this. I can't recall what they are off the top of my head, but honestly, you should probably be using the Github version of code instead. |
I tried to use a latest version but it throws me errors:
and won't allow to proceed. It is working fine with the pervious version. And I have a lot other tokens. |
These errors have nothing to do with files and are probably due to a bad |
I don't know what could be wrong here (and it worked fine with previous version):
|
You don't show how you're creating the lexer and the error messages reference variables that aren't even defined in the above code sample. So, hard to say. |
I build it as: self.clex = lexer(
error_func=self._lex_error_func,
on_lbrace_func=self._lex_on_lbrace_func,
on_rbrace_func=self._lex_on_rbrace_func,
type_lookup_func=self._lex_type_lookup_func)
self.clex.build() |
I don't know what this |
this is a class with all the definitions. Like this |
Will have to investigate further. Do you know the last known version of PLY that worked with this? |
This version worked:
|
And what are you doing exactly? Is the goal to simply use pycparser or is something else going on? Are you extending it? |
I just used it as a template for my own parser (for another custom language). |
I made changes and it is working now. |
I tried to read and understand the documentation about creating and using those file. My goal is not to create those files every time user runs my app (command line). What is the right procedure?
The text was updated successfully, but these errors were encountered: