Timeline for Class invalid flag vs exception
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 26, 2018 at 15:33 | vote | accept | Sandro4912 | ||
| Mar 20, 2018 at 16:20 | answer | added | nvoigt | timeline score: 1 | |
| Mar 20, 2018 at 15:40 | comment | added | BobDalgleish |
You could also use the std::optional facility in C++ to return either an empty result, indicating invalid, or a valid result.
|
|
| Mar 20, 2018 at 13:59 | answer | added | Becuzz | timeline score: 7 | |
| Mar 20, 2018 at 13:38 | answer | added | Jerry Coffin | timeline score: 1 | |
| Mar 20, 2018 at 12:33 | review | Close votes | |||
| Mar 26, 2018 at 3:01 | |||||
| Mar 20, 2018 at 12:14 | comment | added | Robert Harvey | The better practice is the one that best meets your specific requirements. Exceptions can be expensive, so unless you intend to stop processing when an error occurs, throwing an exception on every parsing error could dramatically impact your parsing performance. | |
| Mar 20, 2018 at 12:14 | comment | added | gnat | Possible duplicate of Are exceptions as control flow considered a serious antipattern? If so, Why? | |
| Mar 20, 2018 at 12:12 | review | First posts | |||
| Mar 20, 2018 at 13:20 | |||||
| Mar 20, 2018 at 12:09 | history | asked | Sandro4912 | CC BY-SA 3.0 |