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

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