Jump to content
  • Advertisement

Archived

This topic is now archived and is closed to further replies.

samgzman

Self destructing object?

This topic is 5402 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Advertisement
An example from COM: All COM objects implement the functions AddRef() and Release(). These allow reference counting. Whenever a COM pointer is copied and used by someone else, they call AddRef(), and the internal counter is incremented. Whenever someone is done with a COM object pointer, they call Release(), and the internal counter is decreased. If it becomes zero, then the object deletes itself. It might look a bit like this:

unsigned long SomeObject::Release()
{
--mRefCount;
if (mRefCount == 0)
{
delete this;
return 0;
}
else
{
return mRefCount;
}
}


[Edit - forgot "SomeObject::" part of the function definition. Doh!]

[edited by - Agony on February 6, 2004 3:29:36 PM]

Share this post


Link to post
Share on other sites
Yeah it''s possible.

But you don''t say "~ClassName()" or "delete pToMyself;" Just write "delete this;"

As you can imagine, there are are dangers. This faq entry does a good job of summing up those dangers.

Share this post


Link to post
Share on other sites

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!