Exception Handling

Question

I work in a code base (C # 3.5), which is dotted with exception handling blocks that return true / false when internally in a function that returns 'bool'.

catch (Exception ex) { return false; }

This is the wrong practice. I am thinking of registering an exception and having a local variable (for a function) that will be initialized. And this variable will be returned at the end of the function.

What do you think?

Answer 1

The usual accepted way to handle exceptions is to handle them only if you can do something with it . Of course, you can handle the general exception only for magazines, but after that you have to re-raise.

. , , , ...

Answer 2

catch , .

, - .

catchall, ( ).

Answer 3

, .

C, true/false . # .

, .

, , , . .

Answer 4

, . , (, ), , . , dbase, .

, . , , try/catch, . AppDomain.UnhandledException, , , . , , . , , , , .

Answer 5

, , , !

Answer 6

bool , , .

Answer 7

, false - , , , .

, , .