Skip to main content

C++11 - noexcept function specifier

Today I would like to present another new feature of C++11 standard - noexcept specifier. This specifier allows to specify function which does not throw any exception. It should be used be used wherever possible to notify user that function should be throw and it makes such function non-throwable self-documented (similar to usage const).

Its usage is similar to usage const function specifier. The difference is that while const function tries to modify data it we have compilation error. In case of noexcept function throws any exception, code compiles, however it std::terminate function is invoked when we achieve throwing exception in such function. To understand it better, take a look on below example: Output of this example is: In point I, we are defining function as non-throwable using noexcept specifier. Such function should not throw, however in our example we are throwing exception in order to present what happens when noexcept function tries to throw exception.

In point II, we are defining additional funciton which we will set up as our terminate function.

We are assigning that funtion as terminate function in point III and replacing default std::terminate function by our terminateFunction(). This function will be invoked when we will try to throw any exception in our noexcept testFunction().

In point IV we are invoking our testFunction() which is noexcept function. However, because our function throws any exception and is specified as noexcept our customized std::terminate function (terminateFunction()) will be invoked and application will abort dumping core file (which is visible in last line of output which we received from out example).

Example used above you can find on our GitHub account here: https://github.com/xmementoit/CppAdventureExamples/tree/master/cpp11/noexcept

Comments

Popular posts from this blog

Blog's new layout

As you noticed this blog has new layout from today. I hope you like it. I think new layout looks better and more modern than previous one. Please, write you opinion about new layout in comments. If you have some ideas how to make this blog better, all ideas are welcomed. Enjoy new layout and blog articles.

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...

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...