base32/base64/basenc: implement and test proper flag parsing #6007
Conversation
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
It's good that all encodings already work. Let's make sure they cannot regress!
This was referenced Feb 24, 2024
|
Thanks :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 fixes several issues:
basencwas not tested – it already works, yes, but let's make sure it doesn't regress.basencshould not decide according to some arbitrary built-in priority list (ENCODINGS), but rather let the last encoding on the command-line override any earlier ones. (This fixes a GNU behavior bug.)-d,-i, and-w. (This fixes a GNU behavior bug.)This fixes #5998 for the special case of
base32,base64, andbasenc.