Skip to main content

Advanced C++ - Exceptions

Exception handling is programming feature helpful for programmers to handle run time error conditions.

Run time error conditions can be like division by zero, unable to allocate memory due to scarcity, trying to open a file which doesn’t exist etc. There are two types of exceptions. One is Standard exceptions provided by C++ Standard library and other type is User defined exceptions.

Now, to handle any exception, we should understand 3 main block of exception statement which are as follows:
  • throw block - in this block, we throw an exception. The operand of the throw statement decides the type of exception occurred. Once this line is executed, program jumps to catch block to handle the exception occurred.
  • catch block - is the block where we handle exception. This is also called as exception handler and this block is written immediately after the try block as shown in example. This can be written similar to a normal function with at least one argument preceding with catch keyword. We can have more than one handlers with different type of arguments. Then, only the handler that matches its type of argument with the type of the argument mentioned in throw statement is executed. Also, we can have ellipsis (…) as an argument of the handler i.e catch (…). That time, irrespective of type of argument used in throw statement, this handler is executed. We can also have nested try-catch blocks. After catch block is executed, the program execution resumes after the try-catch block but not after the throw statement.
  • try block - is nothing but that block of code where an exception can occur. This block is followed by one or more catch blocks as required to handle exceptions

Let us see few Standard exceptions examples:
  • bad_alloc
  • - this exception is thrown whenever new operator fails to allocate memory. Refer example “StdException.cpp” which is self explanatory.
  • bad_cast
  • - This is thrown when type conversions fails using dynamic_cast
  • bad_typeid
  • -This is thrown by type_id()
  • Bad_exception
  • - This is thrown when any unexpected exception occurs.

User defined exceptions can be programmed as shown in the below example: Output of that example is as follows: In this example, we show how to handle Divide by zero exception. In class DividerWithException we are throwing exception when divisor is equal 0 (we cannot devide by 0). Then in main function we are using try-catch block to handle exception when it occures and operate it. Thanks to that our program does not crash when we are trying to divide by 0, but we can show some message to user to and notify him about wrong data set pushed to DividerWithException object. Code of this example you can find our our GitHub account here: https://github.com/xmementoit/CppAdventureExamples/tree/master/advancedCpp/excpetions

Comments

Popular posts from this blog

GDB Automatic Deadlock Detector

Have you ever had a problem with detection deadlock between threads in your C/C++ application? Would you like to do that automatically? Try this GDB Automatic Deadlock Detector from my github: GDB Automatic Deadlock Detector Picture source: http://csunplugged.org/wp-content/uploads/2015/03/deadlock.jpg1286488735

STL - count and count_if algorithms

One of the basic and most useful STL algorithms is algorithm which can be used to count number of elements within selected container according to specified criteria. In order to do that we can use std::count or std::count_if algorithm. std::count (firstElementIterator, lastElementIterator, elementForSearch) - is function which will go through container using firstElementIterator and lastElementIterator and return number of container elements which value is equal elementForSearch std::count_if (firstElementIterator, lastElementIterator, UnaryPredicateFunction) - is function which examine range from firstElementIterator to lastElementIterator and return number of container elements which fulfill UnaryPredicateFunction criteria. UnaryPredicateFunction is function having following signature: bool functionName(const Type& a) . So, count_if returns number of elements where UnaryPredicateFunction returns true for. For better understanding let's take a

Advanced C++ - Stack unwinding

Stack unwinding is normally a concept of removing function entries from call stack (also known as Execution stack, Control stack, Function stack or Run-time stack). Call Stack is a stack data structure that stores active functions' addresses and helps in supporting function call/return mechanism. Every time when a function is called, an entry is made into Call stack which contains the return address of the calling function where the control needs to return after the execution of called function. This entry is called by various names like stack frame , activation frame or activation record. With respect to exception handling , stack Unwinding is a process of linearly searching function call stack to reach exception handler. When an exception occurs, if it is not handled in current function where it is thrown, the function Call Stack is unwound until the control reaches try block and then passes to catch block at the end of try block to handle exception. Also, in this proc