Re: AddRef/Release side effects - is this ok?

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Sun, 6 Sep 2009 09:01:49 -0400

Message-ID:

<eB6c7IvLKHA.5460@TK2MSFTNGP02.phx.gbl>

Igor R. wrote:

Once upon a time, if my memory doesn't betray me, I read that
IUnknown's AddRef and Release functions should not have any side-
effects, besides incrementing/decrementing the ref.count.

Well, Release has a mother of all side effects - it destroys the object
when the ref count reaches zero.

This is
because COM proxy might not actually forward these calls to the stub,
or something like that...

The proxy never forwards these calls to the stub, except the very last
Release call when the proxy's own reference count reaches zero and it
destroys itself.

In my case I have to override Release method to notify the object when
ref.count drops to 1.

Why? What are you trying to achieve?
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925