Timeline for strtoul behavior between C and Arduino
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2019 at 12:38 | vote | accept | Nico | ||
| Jun 6, 2019 at 11:37 | answer | added | JRobert | timeline score: 0 | |
| Jun 6, 2019 at 9:39 | answer | added | Majenko | timeline score: 0 | |
| Jun 6, 2019 at 9:00 | comment | added | Nick Gammon♦ | Please make an answer, don't post an answer as a comment. Comments are for clarifying the question. | |
| Jun 6, 2019 at 5:30 | comment | added | KIIV |
Btw first two are caused by difference between: char str[] = "620004"; and uint8_t byteBuffer[] = "620004";
|
|
| Jun 6, 2019 at 5:24 | comment | added | KIIV |
All those errors are related to (char[3]) {byteBuffer[i], byteBuffer[i + 1], '\0'}, it has nothing to do with strtoul. Who knows how old is the compiler where it works.
|
|
| Jun 6, 2019 at 3:50 | review | First posts | |||
| Jun 6, 2019 at 6:16 | |||||
| Jun 6, 2019 at 3:48 | history | asked | Nico | CC BY-SA 4.0 |