Timeline for Better way of handling pre conditions and logging
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 4, 2015 at 9:27 | comment | added | Arseni Mourzenko | I see. Sorry, but since this is specific to C++, I can't help you more. It seems that you can still use exceptions, even if it's not the ideal solution. | |
| Aug 4, 2015 at 9:20 | comment | added | dyesdyes | Yes but asserts are only used in debug mode, I can't rely on them for production code. And also, if the condition is not met, I definitely don't want to stop the program, I just want to log then return, not more, not less. | |
| Aug 4, 2015 at 9:16 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 |
deleted 18 characters in body
|
| Aug 4, 2015 at 9:15 | comment | added | Arseni Mourzenko | @dyesdyes: I see. This being said, the article you link to suggests to use assertions instead, which is a perfectly viable alternative. | |
| Aug 4, 2015 at 9:11 | comment | added | dyesdyes | Forgot to mention it, but this is in C++. And from what I have seen, it's not such a good idea to extensively use the exceptions (stackoverflow.com/questions/4506369/…) | |
| Aug 4, 2015 at 8:52 | history | answered | Arseni Mourzenko | CC BY-SA 3.0 |