Smart Pointer that supports subclassing

Until now all smart pointer implementations that I have seen didn't support assignment between base and derived class pointers. Here is an implementation that does support it. I give you two implementations of smart pointers:

1) Ptr<T> - This smart pointer assumes that 'T' support reference counting by deriving from IRefCount (which is also supplied).

2) SmartPtr<T> - This smart pointer is more generic than Ptr<T> while not assuming anything about the type 'T'. Being more generic costs having a small reference object created for each referenced object or type.

The following source code demonstrates the use of the two types of smart pointers templates.

#include <string>
#include <iostream>
#include "ptr.h"
#include "smartPtr.h"

using namespace std;

class Object;
class Host;

typedef Ptr<Host>			PHost;
typedef Ptr<Object>			PObject;

class Object : public IRefCount {
		Object (int id, const string& name) : m_name(name), m_id(id) {};
		const string& GetName () { return m_name; }
		string	m_name;
		int		m_id;

class Host : public Object {
		Host (int id, const string& name, const string& hostName):
				m_hostName(hostName), Object (id, name) {};
		string	m_hostName;

// The following two classes do not carry any
// reference counting inteface.
class Base {

class Derived : public Base {
typedef SmartPtr<Base>		PBase;
typedef SmartPtr<Derived>	PDerived;

void PrintName (PObject pObj)
	cout << pObj->GetName() >> endl;

// testSmartPtr
// demonstrate the SmartPtr<T> template. The
// Base and Derived classes are simple classes
// that don't support any reference counting.
void testSmartPtr ()
	PDerived pDerived2;
	PBase pBase;

	PDerived pDerived = new Derived;
	// The Ptr<T> supports subclassing
	pBase = pDerived;
	pDerived2 = (PDerived&)pBase;

// testPtr
// demonstrate the Ptr<T> template. The Ptr<T>
// assumes that the referenced class 'T' supports
// the reference counting interface IRefCount.
void testPtr ()
	PHost pHost2;

	PHost pHost = new Host (1, "Wks5", "");

	// The Ptr<T> supports subclassing
	PObject pObject = pHost;		  
	pHost2 = (PHost&)pObject;
	PrintName (pHost2);

 | NAME: main
void main ()
	testSmartPtr ();
	testPtr ();


Download demo project - 6 Kb
Download source - 3 Kb


  • Trouble in std::list

    Posted by maquanwei on 04/26/2004 10:33pm

    I use this smart-point to a std::list, such as std::list>. When I use list::remove(somePtr), my compile give me a C2593 link error. I had to overide operator "==", but SmartPtr does not support compare between base-class's pointer and sub-class's pointer now. Do you have any suggest?

  • No Error - Look more carefully!

    Posted by Legacy on 06/21/2002 12:00am

    Originally posted by: Erez Efrati

    If you just looked more carefully at the source code of the 
    template SmartPtr<T> and RefCountRep<T> you would have seen

    1) RefCountRep<T> is holding a pointer to the actual real
    class, and the following is a piece of the destructor code
    (taken from the SmartPtr.h) :

    template <class T>
    RefCountRep<T>::~RefCountRep ()
    assert (m_count == 0);

    if (m_ptr != 0)
    delete m_ptr;

    template <class T>
    void RefCountRep<T>::ReleaseRef ()
    assert (m_count > 0);

    if (m_count == 0)
    delete this;

    2) Second and more important is that the whole idea about
    having a RefCountRep<T> template is not having the "real"
    class derive any special base class.

    Hope that answers it,


  • Error - your destructor in RefCountRep must be virtual

    Posted by Legacy on 12/18/2001 12:00am

    Originally posted by: NMTop40

    In RefCountRep, your destructor must be virtual! (This is serious). Presumably your template smart pointer will contain a class derived from RefCountRep.

    When it calls ReleaseRef() (on mine I call it Release to be consistent with COM, and indeed my smart pointer class can be used with CComObject classes, something CComPtr does not allow) - anyway - ReleaseRef() will call delete this on RefCountRep but if the destructor is not virtual it will not call the real class's destructor and there may be memory leaks if the real class has allocated memory.

    One other small matter - in mine I made the reference count mutable and the AddRef() and Release() functions const. This allows you to have reference counting on const pointers.

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Anthony Christie, the Chief Marketing Officer for Level Communications, is responsible for customer experience, worldwide marketing and product management. In this informative asset, he shares his insights into why a private network connection to cloud-bases applications is the right decision for your enterprise. Download now to find out more.

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date