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

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

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

Advanced C++ - Template Functions

Template function are special types of C++ function which can be used with different types (generic types). Thanks to that we can create one body of function which can be used for many different types. When we are creating template function compiler does not define any function for use at that time. Generation of funciton basing on templates are done during compilation process basing of differnt usage of template class. For better understanding take a look on following example: Output of this example is: In point I, we are defining template function which should return sum of two parameters. Without templates we need to define such function separately for each type which we should use it with (ex. separate function for int type, separate for double , separate for any other type). Thanks to template we can generate body of that function only once (as in point I) and use it to any type which is able to use body of that function. In our example we can use this template for an...
Post a Comment
Read more