Timeline for Handling exceptions for providing log information while debugging
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 6, 2014 at 10:35 | history | edited | Razor | CC BY-SA 3.0 |
added 517 characters in body
|
| Aug 5, 2014 at 11:36 | vote | accept | ThunderDev | ||
| Aug 5, 2014 at 8:18 | comment | added | Nikita B | This is good design. It is not always possible to follow it though. For example, if you are developing some framework or class library, you might want to do both: log critical exceptions to some local log file (so you can ask for it when angry mob starts throwing rocks at you) and rethrow exception for external code to handle. If you are developing a stand alone application, then you should follow Vince's advice and catch exceptions you can't handle straight away on the highest possible level. | |
| Aug 5, 2014 at 7:39 | comment | added | ThunderDev | Your approach seems the cleanest and will make the code more readable. I'm going to remove the try/catch from the parse method, and only catch higher up if there's something to handle. Global handlers seem like a good idea. No one has commented yet, but could you see any drawbacks from doing this ? Cheers | |
| Aug 2, 2014 at 9:44 | history | answered | Razor | CC BY-SA 3.0 |