Timeline for Should you throw an exception if a method's input values are out of range?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot | replaced http://stackoverflow.com/ with https://stackoverflow.com/ | |
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| May 13, 2014 at 18:19 | history | edited | gnat | CC BY-SA 3.0 | spelling, formatting |
| May 13, 2014 at 12:53 | comment | added | Nathan | Good point. As you're link states, Trace.Assert is the one you would need for a release build, if you have enabled it. | |
| May 13, 2014 at 12:43 | comment | added | nmclean | Assertions are often automatically disabled when not debugging (Debug.Assert will only be called when the debug flag is set), so it's more than just semantics / consensus. | |
| May 13, 2014 at 9:21 | review | First posts | |||
| May 13, 2014 at 10:07 | |||||
| May 13, 2014 at 9:19 | history | edited | Nathan | CC BY-SA 3.0 | added 162 characters in body |
| May 13, 2014 at 9:02 | history | answered | Nathan | CC BY-SA 3.0 |