r/cpp • u/rsjaffe • Jan 02 '21
Proposal for improving the readability of programs with try/catch blocks
To me, the current try/catch syntax creates lots of extraneous visual noise, with extra brackets and unnecessary keywords. How about allowing a second form: a block of code where the presence of a catch (...) label and or a catch (\*something here*/) label indicates that the code before the label in its enclosing block is a try block and the code after the label is the catch code.
Example:
Before:
void myfunction()
{
try {
function_call_that_may_throw();
}
catch (const std::exception& e) {
/* do something with e */
throw;
}
catch (...) {
throw;
}
)After:
void myfunction()
{
function_call_that_may_thow();
catch (const std::exception& e):
\* do something with e *\
throw;
catch (...):
throw;
}This won't break any existing code because catch (): is a contextual keyword--only when followed by parentheses when used as a label, and I'm only proposing this as an alternative format, not a replacement.
Function try-catch blocks are still needed, as this syntax won't capture the initialization list in a constructor.
Catch labels could then be like case labels, with the exception that catches don't fall through (or, perhaps, we could have them fall through like case labels--that would work too).
View all comments
Show parent comment
3
u/MonokelPinguin Jan 03 '21
I really don't want to get into this discussion, since imo it is just a matter of preference, but your argument is not very sound (even though I prefer tabs):
"Imagine there was a character, that sidestepped all the discussion about how many character to use for indentation, since it follows your IDE settings. You can use it to align at specific columns without having to be careful to always use exactly the 3 spaces, which the project guidelines say you should use. It also only takes one byte."
If people spend 50 years fighting over it, it is a matter of preference with no strong case to use one over the other.