Timeline for Advice for bugfixing object oriented code: why is data not set?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 21, 2017 at 16:31 | audit | First posts | |||
| Sep 21, 2017 at 16:34 | |||||
| Sep 15, 2017 at 7:52 | vote | accept | Mark | ||
| Sep 15, 2017 at 5:07 | comment | added | user1118321 | This is a good answer, but it would be nice if you would elaborate on the 4 points, perhaps with some examples. | |
| Sep 14, 2017 at 23:25 | comment | added | Frank Hileman | I would add, set or change each piece of state in as few places as possible. And keep your call chain from higher to lower level objects, avoiding calls from lower level to higher level, as typically occurs in callbacks. | |
| Sep 14, 2017 at 16:05 | comment | added | Robert Harvey | They can. Better state management only reduces the risk; it does not eliminate it. | |
| Sep 14, 2017 at 16:04 | comment | added | Caleth | "obscure bugs do not" -> "obscure bugs cannot"? | |
| Sep 14, 2017 at 16:03 | history | answered | Robert Harvey | CC BY-SA 3.0 |