Re: need argument for try catch blocks
"Edek" <edek.pieITAKNIECZYTAM@gmail.com>
If they do anything that is necessary or of value, they should be there.
Naturally, the project formal/informal policy is one thing to follow, but
in general such 'extra' try-catches are done for example:
a) to clean up resources (like DB, if destructors are not enough), then
they are necessary
Hell no. Resources must be handler by RAII, and never left to hang around
"raw". And mandatory release code must not be multiplicated at every
possible exit.
c) to log, if there are no stack traces and for some reason a debugger
cannot be used, or just it is quicker to have a log without plugging in a
debugger
Logging is a suspicious reason, and if really needed also can be done better
in a RAII-like form. Though special cases may apply.
d) to work around caller code, which does not really handle exceptions, or
handles just a few types - then catching is better than terminate()
I'd rather call it "when exceptions must be converted to error return codes
for the caller".