Handling non-local errors at runtime (part 1)

On this page

Handling non-local errors at runtime
Exceptions
Questions

This lesson contains approximately 30 minutes of video content.

Handling non-local errors at runtime

Exceptions

Errata: On the slide titled Exceptions we write that the catch-block is followed by an exception handler. We meant to write that the try block is followed by an exception handler that specifies the types of objects that it can catch.

Questions

QExceptions, Q1

This question is ungraded.

You should write code that might throw an exception that you'd like to handle under a block.

`catch`

`finally`

`throw`

`try`

Practice question: try as many times as you like

QExceptions, Q2

This question is ungraded.

Exception handlers are introduced after the try-block using the keyword .

`catch`

`finally`

`throw`

`try`

Practice question: try as many times as you like

QExceptions, Q3

This question is ungraded.

Given,

double AreaRectangle(double width, double height) {
  double area = width * height;
  if (area < 0)
    // do something
  return area;
}

best practice dictates that line-4 should:

`catch` a `throw`n `std::invalid_argument` object

`return width * height`

`throw` an exception

`try` to compute `width * height`

Practice question: try as many times as you like

QExceptions, Q4

This question is ungraded.

If an exception is thrown, but is not caught, then

A compile-time error will result during compilation.

Execution will commence after the final `catch` block is evaluated.

Execution will continue in the caller.

The program will terminate.

Practice question: try as many times as you like

QExceptions, Q5

This question is ungraded.

True or false: best practice suggests that we should use exceptions to handle not only non-local errors, but local errors too!

False

True

Practice question: try as many times as you like