Timeline for Recommend a design pattern/approach to exposing/tolerating/recovering from system errors, Exception handling (e.g.s in Java, C++, Perl, PHP)
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 27, 2011 at 5:57 | history | edited | Jalayn | CC BY-SA 3.0 |
spelling
|
| Sep 20, 2011 at 10:02 | history | edited | mikera | CC BY-SA 3.0 |
added 357 characters in body
|
| Sep 20, 2011 at 9:23 | vote | accept | therobyouknow | ||
| Sep 19, 2011 at 19:10 | comment | added | therobyouknow | +1 @Steve A. Lowe - for user-centred design. e.g. like saving files, not leaving temp files lying about. See my question about "data hygiene" as a related topic in my questions list. | |
| Sep 19, 2011 at 19:08 | comment | added | therobyouknow | +1 @mikera for clear points about what to consider. Likely accepted answer, I will leave open for a little longer for others to contribute. | |
| Sep 19, 2011 at 18:23 | comment | added | Steven A. Lowe | also fail gracefully - clean up before terminating if at all possible | |
| Sep 19, 2011 at 15:36 | history | answered | mikera | CC BY-SA 3.0 |