tr: Add ambiguous octal escape warning #6886
Open
+42
−8
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
OshinoShinobu-Chan
force-pushed
the
main
branch
from
e801364
to
30a4724
Compare
|
GNU testsuite comparison: |
OshinoShinobu-Chan
force-pushed
the
main
branch
from
30a4724
to
6954ad9
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 PR is to fix issue #6821.
I add
parse_octal_up_to_three_digits_with_warningwhich is similar toparse_octal_up_to_three_digitsbut can print warning. Becuaseparse_octal_up_to_three_digitsis alse used in other cases, and those cases should not output the warning. With two versions, we can avoid printing the same warning more than once.Some of the other functions are also added "with_warning" version.