comp.lang.idl-pvwave archive: archive » Re: object reference destroy

Home » Public Forums » archive » Re: object reference destroy

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: object reference destroy [message #67051 is a reply to message #67049]

Wed, 24 June 2009 11:33

BlackMage
Messages: 2
Registered: August 2008

Junior Member

An alternative is to implement reference counting. I have implemented
this for my own code and found it very effective, all my classes have
the reference counting class as the root of their inheritance. When
the reference-counting object is created or another object tells it
that it 'owns' a reference to it, the count increases. Once other
objects no longer need the owning reference, they tell the reference-
counting object and the count decreases. Once the count hits zero, the
reference-counting object destroys itself. If the reference-counting
object is destroyed with a non-zero count, it complains and this
assists debugging.

This approach has been very effective for me in object management as I
am no longer trying to work out exactly what part of my code holds the
final reference to any given object so I can destroy it when, and only
when, it is no longer needed. It's especially useful if you have
multiple collections of the same object references e.g. search trees
or linked lists.

Report message to a moderator

[Message index]

		Re: object reference destroy By: David Fanning on Wed, 24 June 2009 11:42
		Re: object reference destroy By: BlackMage on Wed, 24 June 2009 11:33
		Re: object reference destroy By: Doug Edmundson on Mon, 22 June 2009 09:30
		Re: object reference destroy By: greg.addr on Mon, 22 June 2009 05:40
		Re: object reference destroy By: David Fanning on Mon, 22 June 2009 05:27

Previous Topic:	IDL 7.1.1 Workbench update for Macintosh OS X
Next Topic:	Re: AT&T Usenet Netnews Service Shutting Down

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Nov 30 09:02:58 PST 2025

Total time taken to generate the page: 1.19964 seconds