Timeline for Limits of Defensive Programming acknowledging that Exception Handling should be avoided
Current License: CC BY-SA 4.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 18, 2018 at 4:21 | vote | accept | Lefteris008 | ||
Sep 17, 2018 at 14:26 | comment | added | Erik Eidt |
You could do selectedUser.Equals(user.departNameEn) instead.
|
|
Sep 17, 2018 at 11:19 | comment | added | jk. | blogs.msdn.microsoft.com/ericlippert/2008/09/10/… | |
Sep 17, 2018 at 10:29 | answer | added | Baldrickk | timeline score: 7 | |
Sep 17, 2018 at 8:46 | answer | added | Walfrat | timeline score: 0 | |
Sep 17, 2018 at 8:39 | answer | added | Pieter B | timeline score: 1 | |
Sep 17, 2018 at 8:12 | answer | added | nvoigt | timeline score: 12 | |
Sep 17, 2018 at 7:50 | review | Close votes | |||
Sep 22, 2018 at 3:05 | |||||
Sep 17, 2018 at 7:41 | comment | added | Lefteris008 | @gnat Please read my updated last paragraph. I am not asking (again) if Exception Handling is better than Defensive Programming; from the introduction, you can see that I am fully against exceptions to only when really necessary. What I am actually seeking advice for, is if Defensive Programming under certain cases, becomes computationally expensive. | |
Sep 17, 2018 at 7:41 | answer | added | Kilian Foth | timeline score: 3 | |
Sep 17, 2018 at 7:36 | history | edited | Lefteris008 | CC BY-SA 4.0 |
added 354 characters in body
|
Sep 17, 2018 at 7:33 | comment | added | gnat | Possible duplicate of Are exceptions as control flow considered a serious antipattern? If so, Why? | |
Sep 17, 2018 at 7:32 | history | asked | Lefteris008 | CC BY-SA 4.0 |