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

GDB Automatic Deadlock Detector

Have you ever had a problem with detection deadlock between threads in your C/C++ application? Would you like to do that automatically? Try this GDB Automatic Deadlock Detector from my github: GDB Automatic Deadlock Detector Picture source: http://csunplugged.org/wp-content/uploads/2015/03/deadlock.jpg1286488735

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

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