Skip to main content

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

Point III is key point of our example. As you noted testObject is const therefore we cannot modify its constInt and nonConstInt members (you can try uncomment first two lines before point III and you will see compilation error, that you are trying to modify read-only object.). However modification of mutableConstInt is possible despite that testObject is const. We are assigning value 300 to that member field. It is possible thanks to mutable class field feature.

In point IV we are printing values of testObject after modification. As you can see mutableConstInt's value is really changed and is equal 300 now.

Code of this example you can find in our GitHub repository: https://github.com/xmementoit/CppAdventureExamples/tree/master/advancedCpp/mutableMemberField

If you have any questions, please ask in the comments.

Comments

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