You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears as though the fix for #1796 did not solve the issue.
I couldn't understand originally why, as it appears to just be a different method of doing what I had suggested.
It appears in ESP8266 toolchain (like ARM, but unlike AVR) char defaults to UNSIGNED. Which means it never returns -1 and results in infinite loops elsewhere in the code (parseInt in this case).
Shouldn't peek be an int (consistent with read)?
Should ESP8266 Arduino use -fsigned-char to default chars to signed?
just define peek as signed char? (my current workaround)
It appears as though the fix for #1796 did not solve the issue.
I couldn't understand originally why, as it appears to just be a different method of doing what I had suggested.
Upon further investigation the issue is here:
It appears in ESP8266 toolchain (like ARM, but unlike AVR) char defaults to UNSIGNED. Which means it never returns -1 and results in infinite loops elsewhere in the code (parseInt in this case).
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: