A. Division by zero is an exception while opening an input file that does not exist is not an exception.
False. The given except is not related to file operation
B. Suppose you use the assert function to check if certain conditions are met. If the conditions are not met, then the assert function terminates the program.
True. Yes, it terminates by giving error message
C. One way to handle an exception is to print an error message and exit the program.
True. Yes, it is one of the safe way to handle exception and stop the program smoothly
D. All exceptions need to be reported to avoid compilation errors.
False. Exceptions are related to run time.
E. Every try block must have a catch block.
True. A “try block” needs to have catch block but “finally” is optional. There can be more than one catch block for a single “try block”.
F. The order in which catch blocks are listed is not important.
False. It is important to have a good programming skill. If you place the “Exception class” which is the base for all the other types of exception in the top of catch list then, no other specific exception will get caught which is a very bad programming.
G. If an exception is thrown in a try block, the remaining statements in that try block are executed after executing a catch block.
False. “Try block” will not get executed.
H. In C , an exception is a value.
True
I. The class invalid range deals with the string subscript out of range error.
True.
J. In C , any class can be considered an exception class.
False
K. The exception class must contain at least one member.
ans: True
L. An exception can be caught either in the function where it occurred, or in any of the functions
that led to the invocation of the method.
True. But it is always better to catch exception in the same function.
M. When the function call stack is unwound, the function in which the exception was not caught terminates, but the memory for its local variables remains allocated.
True
