You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's 2023 and it's time to rewrite the section on exception categories (or remove it completely if you think it's not a settled subject) because in it's current state is causing harm.
Robert Martin said it already in 2001, and in 2023 it's clear as dailight.
Use CX_NO_CHECK.
In exceptional cases, when you want customers of your software to acknowledge exceptions that it might throw, consider wrapping a CX_CHECK exception around them in your public API layer (for example when developing a code library for sale).
Never use CX_DYNAMIC_CHECK, as it's just an checked exception that can't be caught by it's name, it's always better to just use CX_NO_CHECK
The text was updated successfully, but these errors were encountered:
Thanks for pointing that out, I added a comment in #138.
I guess what is an exceptional case for me, might be the usual case for others. It all depends on what kind of code you're working on...
It's 2023 and it's time to rewrite the section on exception categories (or remove it completely if you think it's not a settled subject) because in it's current state is causing harm.
Robert Martin said it already in 2001, and in 2023 it's clear as dailight.
The text was updated successfully, but these errors were encountered: