Skip to main content

Advanced C++ - Compiler generated functions

When we define some class in our C++ code, compiler is generating some important functions for our class (unless we define it explicitly).

Those functions (sometimes called Compiled Generated Functions) are:

  •  default constructor 
  •  destructor 
  •  copy constructor 
  •  copy assignment operator 

During compilation, compiler knows our code and classes usage, so when we are using one of above functions implicitly, it generate that function implicitly for us in the class body.
For better explenation, let's see the example below:

In point (I) we are defining class TestClass. This class seems to be empty. However we are implicitly using following function in main class:

  •  point III - we are implicitly using defualt constructor in order to create instance of TestClass - default constructor of TestClass is implicitly generated by compiler 
  •  point IV - we are using copy constructor of TestClass in order to copy instance to instance2 - copy constructor of TestClass is implicitly generated by compiler 
  •  point V - we are using copy assignment operator of TestClass in order to copy instance2 to instance3 - copy assignment operator of TestClass is implicitly generated by compiler 
  •  point VI - destructor of TestClass is implicitly being used - destructor of TestClass is implicitly generated by compiler 

Because above functions are implicitly generated by compiler our class looks as in point II.

However if (for example) we remove line with point V, compiler will detect that we are not using copy assignment operator of TestClass in our code and will not generate that function for TestClass. So compiler generates only those Compiler Generated Functions which we are using in our code.

We can also explicitly switch off generating some of Compiled Generated Functions using default and delete C++11 keywords. It will be described in one of another articles.

 Code of above example you can find on our GitHub repository here: https://github.com/xmementoit/CppAdventureExamples/tree/master/advancedCpp/compilerGeneratedFunctions

Comments

  1. Just to make sure. If I use class TestClass following way:
    void main(){
    TestClass instance;
    TestClass instance 2 = instance;
    }
    Is compiler generating only default constructor, destructor in that situation (copy constructor and copy assignment operator are not generated)?

    ReplyDelete
  2. Yes, you are right. Compiler implicitly generates only those functions which it detects are used in the code. In your example those are: default constructor and destructor.

    ReplyDelete

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

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

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