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

Labels:

Comments

Post a Comment

Popular posts from this blog

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...
Post a Comment
Read more

C++ Multithreading - Race conditions

In the previous C++ Multithreading article I presented you how to pass parameters between threads. Take a detail look on the output of that example once again: In the first line of that output you can notice that output text from two threads is mixed. You are probably wondering why it happens? It is because we are not protecting resources which are shared by two threads (in this example cout stream is shared in both threads) which causes multithreading's phenomenon called race condition . Because threads switching and accessing to shared resources are managed by operating system we do not know when std::cout stream will be accessed by main thread and when it will be accessed by second thread. Therefore in the previous article I mentioned that output of the example can be little different on your computer than my output example. What's more it is possible that this output will be different for few consecutive invoking of the example on the same machine. It is beca...
Post a Comment
Read more

C++14 - Tuple addressing via type

Today I would like to introduce one of new features which will arrive to C++ with new language standard (C++14) which is going to be release in 2014. In order to compile example from this article you need to have compiler supporting C++14 standard. The newest version of GCC supports it. I would like to introduce you features called Tuple addressing via type which allows us to get tuple element value using type name instead of tuple parameter number. Of course it is possible only for type names which are not ambiguous. Let's take a look on below example for better understanding: In point I we are declaring our tuple type containng of 2 int elements and on string element. In point II we are using std::get function to get values of our tuple typed variable using tuple parameters numbers. This feature is well known from C++11 standard. Point III shows new (introduced in C++14 standard) way of getting values of tuple elements. We are getting string type element using...
Post a Comment
Read more