Timeline for Erratic behavior in String based functions
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2021 at 18:15 | comment | added | dandavis | why store literals as String classes instead of cstrings? seems unnecessary.... | |
| Feb 2, 2021 at 3:54 | comment | added | Okabe_ | @timemage I didn't know that. Thank you! I'm sure someone else who's found himself in a corner like me will find this useful! | |
| Feb 2, 2021 at 3:47 | comment | added | timemage | Well, there isn't actually a String constructor for an array of char. There's one for a pointer to const char, which is completely unaware of the size of the array that the pointer was formed from. | |
| Feb 2, 2021 at 3:43 | comment | added | Okabe_ | @Majenko You were right! Apparently the String constructor doesn't handle the null termination with a char array input. Null terminating the string fixed the problem! Thank you! | |
| Feb 2, 2021 at 1:54 | comment | added | Okabe_ | @Majenko I thought converting from char array to String meant it was automatically null terminated? And the reason I have been using char arrays is to not have to deal with the null termination char. | |
| Feb 1, 2021 at 23:09 | history | edited | ocrdu | CC BY-SA 4.0 |
deleted 289 characters in body
|
| Feb 1, 2021 at 23:06 | review | Close votes | |||
| Feb 18, 2021 at 3:03 | |||||
| Feb 1, 2021 at 18:32 | comment | added | Majenko | Two words: "Null termination". You haven't terminated your strings properly. | |
| Feb 1, 2021 at 17:43 | history | edited | timemage | CC BY-SA 4.0 |
Code quoting.
|
| Feb 1, 2021 at 17:27 | review | First posts | |||
| Feb 1, 2021 at 17:43 | |||||
| Feb 1, 2021 at 17:23 | history | asked | Okabe_ | CC BY-SA 4.0 |