Timeline for How assertive should I be in handling exceptions in objects?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 29, 2022 at 8:42 | comment | added | JonasH | "Don't ever use exceptions as part of logic,", cancellationTokens are designed to throw when cancelled. So I think it is exaggerated to never use exceptions for logic. I think avoid whenever possible would be a better claim. | |
| Dec 14, 2011 at 4:35 | comment | added | Akash Kava | I have updated my answer. | |
| Dec 14, 2011 at 4:35 | history | edited | Akash Kava | CC BY-SA 3.0 |
added 920 characters in body
|
| Dec 13, 2011 at 19:57 | comment | added | one.beat.consumer |
+1 Thank you. This is a little more what I was looking for. Some people have said to me 'catch everything an object might throw', others say 'catch e only at the top for clean code', etc... I'm trying to learn best practices... exception as logic is no concern here, but your first three comments are helpful. thank you.
|
|
| Dec 13, 2011 at 19:35 | history | answered | Akash Kava | CC BY-SA 3.0 |