Timeline for What's the best way to handle Windows API errors in response to system messages or when I have nowhere to return them to?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2015 at 8:08 | comment | added | Pieter B | @Deduplicator the harmless error are actually errors where you know what to do with them. | |
| Apr 5, 2015 at 20:55 | comment | added | Alex | @Deduplicator you're right. There are few scenarios were errors can be ignored, however as a general rule it's better to say they can never be ignored. Exceptions to the rule do not change the rule, they're just exceptions. If you think about it there are very few scenarios where you actually have a good reason to ignore an error. | |
| Apr 5, 2015 at 20:42 | comment | added | Deduplicator | If there's nothing to be done for an error, checking for it to ignore it is useless. Also, sometimes errors are harmless and can be simply ignored completely. If those errors are signaled with exceptions, the empty catch-block should contain a good comment. | |
| Apr 5, 2015 at 20:19 | history | answered | Alex | CC BY-SA 3.0 |