Use C++ functions to parse numeric literals and check bounds #108
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
kthielen
reviewed
Apr 2, 2018
| @@ -3,8 +3,7 @@ | |||
| cd `dirname ${BASH_SOURCE[0]}` | |||
|
|
|||
| # generate the LALR(1) parser and token definitions | |||
| bison -d -ohexpr.parse.C hexpr.y | |||
| ${BISON:-bison} -d -ohexpr.parse.C hexpr.y | |||
kthielen
reviewed
Apr 2, 2018
| @@ -1,2 +1,4 @@ | |||
| *.sw? | |||
| /build/ | |||
| CMakeCache.txt | |||
There was a problem hiding this comment.
Oh, good idea. I always build out of a different directory for some reason.
kthielen
approved these changes
Apr 2, 2018
|
Maybe different flex versions; this parser needs some renovation work at some point but it is good to have this fix in mind for any future work (so we don't silently accept and truncate any literal input). |
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.
What's going on with hexpr.lex.C? Was it up to date with hexpr.l?