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

Overhead due to stand-alone parsers/lexers #18

Open
sebastianriese opened this issue Sep 6, 2013 · 1 comment
Open

Overhead due to stand-alone parsers/lexers #18

sebastianriese opened this issue Sep 6, 2013 · 1 comment

Comments

@sebastianriese
Copy link
Owner

Some of the source code of the generated files could be split to a runtime library. This should remain optional/it has to be easy to ship the runtime with any other package using generated parsers.

An extension module runtime library would also allow speeding up the parser transparently, where available (perhaps we would have to get the lex/parse-tables out of the python data structures for more efficient access).

We should also think about cleaner design of the Lexer and Parser classes and extensibility.

@sebastianriese
Copy link
Owner Author

First work on this is done. We loose some options, but the changes have not been propagated to main.py, standalone mode has to be implemented where the entire runtime is copied to the output file

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