Re: Self deleting class

From:

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam>

Newsgroups:

microsoft.public.vc.language

Date:

Thu, 25 Oct 2007 09:35:58 -0500

Message-ID:

<#OOAYRxFIHA.1168@TK2MSFTNGP02.phx.gbl>

"Giovanni Dicanio" <giovanni.dicanio@invalid.it> wrote in message
news:OCxF6zoFIHA.4228@TK2MSFTNGP02.phx.gbl...

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam> ha scritto nel messaggio
news:OJrhfXoFIHA.3768@TK2MSFTNGP06.phx.gbl...

It is often combined with reference counting, a single threaded version
might look like:

       int m_useCount;
       virtual void AddRef() { m_useCount++; }
       virtual void Release() { if (0 == --m_useCount) delete this; }

It is like COM and ATL do (BTW: I believe they work also with
multithreading, maybe they use some multithreading-safe form of
increasing-decresing the counter, but I don't know precisely).

The most common method is InterlockedIncrement/InterlockedDecrement.

IMHO, the OP may consider using ATL for her development. She will have
robust classes and patterns to use to build quality apps, and not spend
time trying to kind of "reinventing the wheel" (see also another thread
about object-oriented C++ development to wrap Win32 APIs using
Get/SetWindowLong, etc.).

True, but it is still important to do it once yourself so you understand how
the frameworks behave.