Fix: use unsigned value to represent bytes #4493
Open
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.
Some variables that represent bytes were found using a signed char type.
Before 3fb3bb5d38r, "configure: force 'char' type to be signed (#4025),
char types could be unsigned, depending on the platform, but now thery are signed.
This intoduces a rough edge on variables that relied on the "unsignedness" of the type char to represent bytes, without actually enforcing it.
This PR addresses that by enforcing the use of "unsigned" type in those cases.