Add "lexparse.h" headers for lexer/parser integration #112
Conversation
This file contains 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
And include them in a few strategic places. This avoids build failures with future compilers that do not support implicit function declarations by default. (NB: This commit does not regenerate the lexers/parsers, so the line numbers are slightly off.)
|
Thanks for the contribution. This is an area I'm not familiar with, so it is especially welcome. I'll have a look as soon as I can. |
giacomini
added a commit
that referenced
this pull request
May 3, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
And include them in a few strategic places. This avoids build failures with future compilers that do not support implicit function declarations by default.
(NB: This commit does not regenerate the lexers/parsers, so the line numbers are slightly off.)
Related to: