Skip to main content

C++11 - Explicit override and final

Consider following inheritance situation:
Question is: will we have two override_func() functions in derived1 or only one because override_func(double a) from derived1 overrides override_func(int a) from base_class? Two, of course. It is because those functions has different signature (different types of arguments in this case). However sometimes user does not notice it and think that function override_func(double a) overrides function override_func(double a) in derived1 class. It can cause problem especially if someone is doing some modifications in override_func(int a) in base class and expects that those changes will have inpact on override_func(double a) from derived1 class. C++11 has smart mechanism which allow to notify compiler and other users that in derived class we would like to override function having exact the same signature in base class. It can be done using override keyword. Let's declare override_func(double a) in derived1 class this way:
What happend's here? We will have compile because using override function we infor compiler (and users) that we would like to override function having exactly the same signature in base class. In our case base class override_func(int a) has int type argument while in derived1 class we have double type argument. Compiler cannot find exact-signatured function in base class so it throws compiler-error. This mechanism is useful for better controlling overriding in C++11. Second useful new C++11 feature related to inheritance and polymorphism is final keyword. If we label function using final keyword, we notify compiler(and user) that such function cannot be overritten in any derived class. Let's see it on example:
While we are trying compile above example we will receive compile error. It is because function final_func() in base class is labeled as final function, so we cannot override it in derived1 class, but we are trying to do that. We can also label class using final keyword. Such label final class cannot be inherited by any other class. Let's see example:
In above example we will receive compile error, because class base is labelled as final. While we are trying to inhert from that class (derived1 class is trying it) compiler notify incorrectness and notify us about it using error message. That's it for today. If you would like to test above features yourself I prepared simple example of above mechanisms. You can compile it and try to compile and modify. Try to uncomment blocks of code labelled as UNCOMMENT and you will compiler errors and behaviours of program according to above examples. This example you can find here: https://github.com/xmementoit/CppAdventureExamples/tree/master/cpp11/explicitOverrideAndFinal
Labels:

Comments

Post a Comment

Popular posts from this blog

Advanced C++ - Mutable Class Field

Today I would like to present C++ class' feature called mutable class field . Mutable class field is class' field modifier which allows to change its value even if object of the class is declared as const . Take a look at the example: Output of this example is: In point I of that example we are defining object of TestClass . Note that this object is const . As you can see in point Ia this class has three different member fields ( constInt, mutableConstInt, nonConstInt ). Those variables are public for this example, but do not worry about encapsulation here. It is just omitted for simplify this example. As you can see one of this member fields is marked as mutable class file using mutable keyword ( mutableConstInt ). Such variable can be modified even if object of class TestClass is const . It will be explained in next points of this example. In point II we are printing default values of testObject object initialized in initialization list of TestClass' default c...
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