suppress line markers from Flex and Bison output #222
Merged
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
This aids reproducible builds, which we have gradually been progressing towards. At this point it seems unlikely the Flex bug¹ that prevents using `%option noline` will ever be fixed. So lets just use the work around for it. ¹ westes/flex#268
Smattr
force-pushed
the
smattr/D152DEF2-BD84-4C95-B8D5-3A0EAC4C9B39
branch
from
0fc4d3a to
205518c
Compare
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.
This aids reproducible builds, which we have gradually been progressing towards.
At this point it seems unlikely the Flex bug¹ that prevents using
%option nolinewill ever be fixed. So lets just use the work around for it.¹ westes/flex#268