Skip to main content

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

Popular posts from this blog

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

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

Advanced C++ - Template Functions

Template function are special types of C++ function which can be used with different types (generic types). Thanks to that we can create one body of function which can be used for many different types. When we are creating template function compiler does not define any function for use at that time. Generation of funciton basing on templates are done during compilation process basing of differnt usage of template class. For better understanding take a look on following example: Output of this example is: In point I, we are defining template function which should return sum of two parameters. Without templates we need to define such function separately for each type which we should use it with (ex. separate function for int type, separate for double , separate for any other type). Thanks to template we can generate body of that function only once (as in point I) and use it to any type which is able to use body of that function. In our example we can use this template for an...