Convert char to unsigned before calling ctype.h functions #1
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.
the
isspace
andisdigit
functions, like many other functions from ctype.h, actually take anint
as the parameter, and are specified to have undefined behavior when the parameter is not in the range (-1)-255. Because it is implementation-defined whetherchar
is signed or unsigned (and on most compilers targeting x86 it is actually signed), if achar
in the range 128-254 (say, because the format string is encoded in a superset of ASCII, including UTF-8) is passed to those functions, it could be sign-extended to (-128)-(-2) and cause undefined behavior.This patch adds manually conversion from
char
tounsigned char
before passing them to ctype.h functions; sinceunsigned char
-to-int
conversion is zero-extension, this avoids said undefined behavior.