Timeline for Maintaining global states in a recursive function
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 14, 2023 at 14:03 | history | edited | candied_orange | CC BY-SA 4.0 |
added 10 characters in body
|
| Nov 14, 2023 at 11:59 | comment | added | gnasher729 | @candied_orange And that is of course 100% true. Except using “public” or “private” also means that the C “plain old data structure” rules don’t apply anymore. | |
| Nov 14, 2023 at 2:23 | history | edited | candied_orange | CC BY-SA 4.0 |
added 4 characters in body
|
| Nov 14, 2023 at 0:43 | comment | added | candied_orange | @Alexander yes. My C++ professor (who was on the language committee) used to love telling us that the only difference between objects and structs was whether or not members defaulted to public. | |
| Nov 14, 2023 at 0:38 | comment | added | Alexander |
And in the case of C specifically here, your can approximate that as a struct, with functions that take a struct instance as a param (akin to this).
|
|
| Nov 14, 2023 at 0:25 | history | answered | candied_orange | CC BY-SA 4.0 |