Search Results

The suggestion of the team to catch the unexpected exceptions in the private functions that each retrieve a section of the page is a very good way to ensure that a failure in one section does not affect …

That tutorial seems to use the term "exception ducking" in a non-conventional way. The code you present is indeed swallowing the exception, by catching it and doing nothing. Ducking an exception mean …

Whether using such complicated expressions in a push back (or any other function call) is debatable and it depends on two factors: 1. your local coding conventions, and 2. the comfort level of you an …

Such different handling is not really possible when all exceptions have the same type. …

Within the C++ community there might be more talk about 'exception safe' code, but it is almost equally important in other languages that have exceptions. …

The main reason for not letting exceptions escape from main is because otherwise you lose all possibility to control how the problem gets reported to your users. …

There are two reasons for catching an exception To convert the exception to a different exception, so that internal implementation details are not exposed to users of a module. An example could be t …

When the processor throws up an illegal instruction error, there are usually so many unknowns about the program state that the easiest way to get into a known-good state is to let the process crash an …

It might be the best way to guarantee that all exceptions get logged. I do have a problem with controllers that consume exceptions without so much as telling the user that their request has failed. …

The throws declaration on a public method should document all the exceptions that a caller of that method might have to deal with (or at least be aware of). … That is not just the exceptions thrown by the method itself, but also the exceptions thrown by functions/methods that it calls and which are not handled. …

Should the exception blocks in a try-except sequence be specific only to those exceptions which may originate from the try? … Or can they be inclusive of exceptions that may arise from handling the original exception caught? …

Exceptions are meant to be fatal if you don't know how to handle them. And just logging that an exception occurred is not handling the exception. …

The choice between exceptions and error codes should not be a global one, but rather based on how exceptional the error condition is with a normal usage of the library. … Exceptions should be used to report serious problems that should not occur with normal usage of the library and that the immediate caller is unlikely to be able to recover from. …

This option is particularly useful if you might want to differentiate between the different exceptions in your catch clauses. …

The relative cost of handling exceptions is the source for the adagio not to use them for flow-control, but what is actually meant is that you should not use exceptions to realize a flow through your program … Exceptions are a perfect tool if you encounter an error and need to bail out of multiple levels of you call stack. …