Timeline for Validation/error handling of user input values
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 19, 2014 at 10:41 | comment | added | Nobody moving away from SE | In this case it might be true (as the newly thrown exceptions are raised at the same level where they are caught) that the exceptions are a disguised goto. However, I would argue that exceptions are a good fit to indicate parsing errors. They have a clear edge over errors that are returned from the function or must be requested via special error functions (like failbit()) because the latter can easily be ignored/forgotten. | |
| Jul 18, 2014 at 23:37 | history | answered | Snowbody | CC BY-SA 3.0 |