Closed
Conversation
Collaborator
|
What is the status of this PR? The OCaml-side one seems ready to merge, should merge it without waiting for the Camlp4 side? My natural inclination would rather be to wait for a @diml - approved patch to be merged here, and merge the ocaml-side branch right after that (without the travis-ci blurb). |
|
The changes to Camlp4Ast2OCamlAst are ready to be merged once ocaml/ocaml#170 is merged. This will ensure Camlp4 builds with trunk. The patch also modifies the token type and the lexer but doesn't change the Camlp4 AST. Unless the Camlp4 AST is updated as well I don't think I'll merge these modifications as it creates incompatibilities for no real benefit. |
Contributor
Author
|
#91 should replace this PR |
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ocaml/ocaml#170
ocaml/ocaml#155
Not ready to merge as it fails to parse non-standard modifier ([^nlL]) and does not give good error msg.