Across
- 4. In general, we want no more____ try block per function/method
- 11. Passing an error code back through multiple layers of calls is error _____ _____
- 13. When an out parameter passes an error code (2 words)
- 14. Put ____ class catch handlers before base class catch handlers
- 15. Keyword for handling an exception
- 17. Inherit your exceptions from the standard ______
- 18. Recommended throwing _______ instead of native types such as int
- 20. We cannot use error codes with _____
- 22. For a catch, the parameters should be by __________
- 23. Keyword to associate code with a catch
- 24. For catch handlers, const and volatile are _____
- 26. When a framework, e.g., MFC, throws pointers, use ______
- 28. After an exception is caught and handled, and the control flow continues right after the throw point is called ______ semantics
Down
- 1. Error codes are not ____ across applications
- 2. C++ only supports ______ semantics
- 3. Unlike some other object-oriented languages, C++ has no _____ keyword
- 5. When a global variable contains the exact error code
- 6. Normal processing is not ____ ____ by exception handling
- 7. After an exception is caught and handled, and the control flow continues right after the catch is called ______ semantics
- 8. Use the specifier _____ if a function/method is not going to throw anything
- 9. The Re-Throw idiom is used for an exception _______
- 10. Propagating an error code is ______
- 12. Do not use exception handling for normal
- 16. If the constructor for an object does not finish, the program never calls the ______
- 19. When the return statement can pass back the error code, sometimes mixed with valid values (2 words)
- 21. When we catch an exception, then use another throw, it is a _____
- 25. RAII should be used for all variables since they automatically _______
- 27. Every field/data member should have ____ semantics