Exceptions

Question 1

What are throwing exceptions used for?

Answer 1

Allows for relevant information to be collected and returned as a bundle when something goes wrong (aids debugging)

Question 2

Should we throw everything?

Answer 2

No. Anything can be thrown but not everything should be thrown.

Question 3

Why should we throw the relevant derived std::exception.

Answer 3

So that users can program separate catch statements to handle each exception individually. Allows for further debugging.

Question 4

What can put in the function declaration to indicate it does not throw an exception?

Answer 4

noexcept

Question 5

What could we do to customise our own exceptions?

Answer 5

• Overriding the what() operation.
• Writing own own functions to provide this information

Question 6

How would we catch multiple different exceptions?

Answer 6

Using multiple catch blocks.

Question 7

Why should we use exceptions with resource allocation?

Answer 7

To help clean up resources.

Question 8

Why should we embrace the RAII? principle?

Answer 8

Allows us to write code that does automatic clean up with exceptions.

Question 9

Why should we embrace abstractions?

Answer 9

Allows us to rely on the code to sort out memory management.