Boost - Scoped pointer

Here is the first article about Boost libraries features. I am starting that new series of articles with explanation of scoped_ptr - one of the Boost smart pointers.

scoped_ptr is smart pointer that is the only owner of dynamically allocated object and is automatically freed allocated memory when destructor of scoped_ptr is called.

See example below:
Output of this example is:

In point I and II we are defining two scoped_ptr pointers - one for int and one for Test (custom class) object.

Notice comment marked as Ia. That is impossible operation for scoped_ptr. It is trying to assign ownership of allocated object to second pointer. scoped_ptr does not allow it. It have to be sole owner of its object.

Point III shows how we can assign new values to object which refers to scoped_ptr. We can use dereference operator (operator*) as for normal pointers (this operator is overloaded in Boost smart pointers) as well as use get() function implemented to Boost smart pointers.

Point IV shows how to use reset function to replace object which is being pointed by scoped_ptr. We can use reset() function for it. After using that function new object will be allocated and old object will be freed automatically. Therefore you can see text: "Constructor of Test class: 2 Destructor of Test class: 1" in the output text.

Take a special look at point V. This is place where we are exiting area of visibility of our scoped_ptr objects. In that place memory allocated for those pointers will be automatically freed. We do not have to use delete function like for normal pointers.

Smart pointers automatically free memory associated with dynamically allocated object which is being pointed by them while scoped_ptr destructor is being invoked.

Code of this example can be downloaded from here: https://github.com/xmementoit/CppAdventureExamples/tree/master/boost/scopedPointer

Comments

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

Developer Adventure

Search This Blog