CPSC 421 OOP Errors and Exception Handling

9. Passing an error code back through multiple layers of calls is error _____ _____
10. We cannot use error codes with _____
11. Normal processing is not _____ _____ by exception handling
12. For catch handlers, the type modifier _____ is ignored
19. When a global variable contains the exact error code it is a _____ _____ _____
21. After an exception is caught and handled, and the control flow continues right after the throw point, this is called _____ semantics
23. Inherit your exceptions from the _____ exceptions
24. Unlike some other object-oriented languages, C++ has no _____ keyword
25. For catch handlers, the type modifier _____ is ignored
26. The keyword for handling an exception
27. When an out parameter passes an error code it is an _____ _____
29. When a framework, e.g., MFC, throws pointers, use _____

1. If the constructor for an object does not finish, the program never calls the _____
2. A _____ is when we catch an exception and immediately throw it again
3. Error codes are not _____ across applications
4. C++ only supports _____ semantics
5. Use the specifier _____ if a function/method is not going to throw anything
6. For a catch, the parameters should be by _____
7. Put _____ class catch handlers before base class catch handlers
8. RAII should be used for all variables since they automatically _____
13. Do not use exception handling for normal _____
14. When the return statement can pass back the error code, sometimes mixed with valid values, it is the _____ _____
15. The keyword to associate code with a catch
16. After an exception is caught and handled, and the control flow continues right after the catch, this is called _____ semantics
17. The Re-Throw idiom is used for an exception _____
18. Every field/data member should have _____ semantics
20. In general, we want no more than _____ try block per function/method
22. Throw _____ instead of native types such as int
28. The code to propagate an error code