From KitwarePublic
< VTK‎ | Tutorials
Revision as of 15:38, 1 February 2010 by ScratchMonkey (talk | contribs) (→‎Idea: compare to standard shared_ptr)
Jump to navigationJump to search


The idea behind smart pointers is reference counting. If the object goes out of scope and it is not being used anywhere else, it will be deleted automatically. This is an important part of writing exception-safe code. With the proper use of smart pointers, you should never seen an explicit Delete invocation in your code. Pretty 'smart', eh?

Note: vtkSmartPointer in combination with the internal reference counting of vtkObject reproduces much of the functionality of the std::tr1::shared_ptr template class introduced in the C++ Standard's Library Extensions Technical Report 1 (known as TR1). (This class first appeared as part of the Boost library.) If you're familiar with shared_ptr, then you already know most of how to use vtkSmartPointer. The principle difference is that, in VTK, the reference count is stored in the object, not the smart pointer. A vtkObject "owns itself", and the special vtkSmartPointer<>::New() method creates an object and smart pointer in one step, with the pointer holding the initial ownership of the object.


Creating an Object with a Smart Pointer

One way to create a VTK object is

vtkObject* MyObject = vtkObject::New();

This method, however, can (and likely will) lead to memory management issues at some point or another. You must manually delete the object


or you will have a memory leak. VTK's solution to this ever-annoying problem is the smart pointer. To use it, you must

#include <vtkSmartPointer.h>

Then you can create an object as follows:

vtkSmartPointer<vtkObject> MyObject = vtkSmartPointer<vtkObject>::New();

Note the special syntax on the right of the assignment. One almost never wants to assign a raw object pointer to a smart pointer, as is done here:

vtkSmartPointer<vtkObject> MyObject = vtkObject::New();

This is almost always a coding error, because the reference count is incremented, requiring an explicit Delete later.

Putting an Existing Object into a Smart Pointer

You may need to wrap a raw pointer because you need to use a constructor that takes arguments. In this situation, use the Take method. This passes the object's self-ownership to the smart pointer:

class MySpecialClass : public vtkObject { /* ... */ };
MySpecialClass* MyObjectRaw = new MyObject(arguments);
vtkSmartPointer<MySpecialClass> MyObject;

Because MyObject now owns the object, there is no need to invoke MyObjectRaw->Delete().

Getting an Object with a Smart Pointer

When not allocating memory for an object, you can still use smart pointers. Take this simple example:

vtkSmartPointer<vtkXMLPolyDataReader> Reader = vtkSmartPointer<vtkXMLPolyDataReader>::New();
vtkPolyData* pd = Reader->GetOutput();


vtkSmartPointer<vtkPolyData> pd = Reader->GetOutput();

In the first case, when the reader object goes out of scope, the data is deleted. In the second case, by using a smart pointer we have incremented the data's reference count by 1, so the data will not be deleted until the reader AND the polydata object go out of scope.

Returning a Smart Pointer


You should define a function like this:

vtkSmartPointer<vtkPolyData> MyFunction()
  vtkSmartPointer<vtkPolyData> myObject = vtkSmartPointer<vtkPolyData>::New();
  return myObject;

And call the function using:

vtkSmartPointer<vtkPolyData> MyPolydata = MyFunction();

The smart pointer in the function is copied to the smart pointer in the caller, so the reference count remains unchanged and the associated object is not deleted.


vtkPolyData* MyFunction()
  vtkSmartPointer<vtkPolyData> MyObject = vtkSmartPointer<vtkPolyData>::New();
  return MyObject;

vtkPolyData* MyPolydata = MyFunction();

In this case, the smart pointer is converted to a raw pointer before being returned to the caller. As the function exits, the smart pointer's reference count goes to zero and the actual object is deleted, leaving the raw pointer dangling, pointing at freed memory.

Using Smart Pointers as Class Member Variables

Smart pointers make class destructors simple, by automatically releasing ownership of shared objects.

Declare the pointer like this:

class MyClass
  vtkSmartPointer<vtkFloatArray> Distances;

You can initialize the smart pointer in your constructor using an initializer:

: Distances(vtkSmartPointer<vtkFloatArray>::New())

Or you can initialize it with an assignment statement:

  Distances = vtkSmartPointer<vtkFloatArray>::New();

There is no need to explicitly Delete the object in your class destructor. By using smart pointers in your classes, your destructors become much simpler. You may find that you don't have to write a destructor at all, as the default destructor will Delete all your objects through the magic of the smart pointer.


  • If you create an object and then change where it is pointing, the reference count will be incorrect. e.g.
vtkSmartPointer<vtkPolyData> Polydata = vtkSmartPointer<vtkPolyData>::New();
Polydata = Reader->GetOutput();

In this case, memory is allocated for Polydata, but then we change Polydata to point to the output of Reader rather than the memory we just allocated. Instead, we should have done simply:

vtkPolyData* Polydata = Reader->GetOutput();

It was not necessary to use a smart pointer because we did not actually create any new objects.


Here is an example of equivalent operations with and without smart pointers:


#include <vtkFloatArray.h>
#include <vtkSmartPointer.h>

void WithSmartPointers();
void WithoutSmartPointers();

int main(int argc, char *argv[])
  return 0;

void WithSmartPointers()
  vtkSmartPointer<vtkFloatArray> Distances = vtkSmartPointer<vtkFloatArray>::New();

void WithoutSmartPointers()
  vtkFloatArray* Distances = vtkFloatArray::New();


cmake_minimum_required(VERSION 2.6)



ADD_EXECUTABLE(SmartPointers SmartPointers.cpp)
TARGET_LINK_LIBRARIES(SmartPointers vtkHybrid)