fix: resolve sign comparison warning in PubSubClient::publish_P #1075
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
|
Welcome to the long list of users fixing this ... ;-) |
|
Thanks for maintaining this library. Unfortunately, PubSubClient3 fail to build when using the SAMD21G18A platform, so I just patched version 2.8 for now. |
|
Can you create an issue at PubSubClient3 and explain what does not work? Do you use |
|
Sure, I'm opening the issue right now. Issue: hmueller01#6 |
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.
Changed the type of
expectedLengthfrominttounsigned intto matchrctype,resolving the -Wsign-compare warning on line 523: return (rc == expectedLength);