CPSC 421 OOP Errors and Exception Handling

5. When a framework, e.g., MFC, throws pointers, use _____
7. Normal processing is not _____ _____ by exception handling
8. The Re-Throw idiom is used for an exception _____
11. Error codes are not _____ across applications
14. RAII should be used for all variables since they automatically _____
15. A _____ is when we catch an exception and immediately throw it again
16. We cannot use error codes with _____
20. If the constructor for an object does not finish, the program never calls the _____
21. C++ only supports _____ semantics
25. After an exception is caught and handled, and the control flow continues right after the catch, this is called _____ semantics
26. For a catch, the parameters should be by _____
28. The keyword for handling an exception
29. Passing an error code back through multiple layers of calls is error _____ _____

1. When a global variable contains the exact error code it is a _____ _____ _____
2. The code to propagate an error code
3. For catch handlers, the type modifier _____ is ignored
4. For catch handlers, the type modifier _____ is ignored
6. In general, we want no more than _____ try block per function/method
9. When the return statement can pass back the error code, sometimes mixed with valid values, it is the _____ _____
10. When an out parameter passes an error code it is an _____ _____
12. After an exception is caught and handled, and the control flow continues right after the throw point, this is called _____ semantics
13. Do not use exception handling for normal _____
17. Put _____ class catch handlers before base class catch handlers
18. Unlike some other object-oriented languages, C++ has no _____ keyword
19. Every field/data member should have _____ semantics
22. The keyword to associate code with a catch
23. Use the specifier _____ if a function/method is not going to throw anything
24. Inherit your exceptions from the _____ exceptions
27. Throw _____ instead of native types such as int