Replies: 1 comment
-
|
I agree ATL doesn't behave like a classic library would in that regard. I expect users to exploit return values and use the logging system, but most other libraries don't hesitate to throw exceptions when a process-breaking issue arises. As a quick fix, I could create a new setting to turn on exception throwing. As most of them are caught in the same place, that wouldn't be too hard to implement. That being said, it's the first time someone actually raises that point. Would you mind explaining why return values and logging don't fit your needs? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is there an easy way to retrieve the internally raised exceptions?
I would prefer if ATL.NET could raise exceptions instead of silently logging them, is that possible? If not, how can I retrieve the exceptions without having to parse the log?
Beta Was this translation helpful? Give feedback.
All reactions