-
Notifications
You must be signed in to change notification settings - Fork 26
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
Use menhir-based parser instead of camlp4o #16
Comments
+1, we should absolutely get rid of camlp4 where possible. @michipili definitely a milestone before 1.0 IMO |
The grammar that the parser implements is documented here. It took forever to find it. Enterprise software is terrifying. |
@rgrinberg Agreed! #12. |
I have a branch (on top of #22) that replaces the camlp4 lexer with with the same lexer but without the syntax extension. It would still be nice to have a proper menhir based parser, but i think that should be enough to solve this problem for the medium term. |
We aren't using camlp4 anymore. |
The library uses camlp4o to parse locale definitions, which is a hinderance to both adoption (see tategakibunko/jingoo#19) as well as future maintenance. The parser should be ported to menhir or some such other parser library to break the dependency with camlp4o.
The text was updated successfully, but these errors were encountered: