Destroying Objects
It is generally the case that after an object is used, it is removed from memory to make room for other programs or objects to take that object's place. In order for this to happen, a destruction method is called upon that object. Destroying an object will cause any references to the object to become invalid.
A destructor is a method called when an instance of a class is deleted, before the memory is deallocated. Note that in C++, a destructor can not be overloaded like a constructor can. It has to have no arguments. A destructor does not need to maintain class invariants.
In garbage collecting languages, objects may be destroyed when they can no longer be reached by the running code. Examples of this are Python and Java. Python has destructors, and they are optional. In many garbage collecting languages, finalizers (which are called before an object is garbage-collected) are used instead of destructors, since the point of garbage-collection is not predictable in these languages. Example of these include Java and Ruby.
Read more about this topic: Object Lifetime
Famous quotes containing the words destroying and/or objects:
“Can we not teach children, even as we protect them from victimization, that for them to become victimizers constitutes the greatest peril of all, specifically the sacrifice—physical or psychological—of the well-being of other people? And that destroying the life or safety of other people, through teasing, bullying, hitting or otherwise, “putting them down,” is as destructive to themselves as to their victims.”
—Lewis P. Lipsitt (20th century)
“He who observes etiquette but objects to lying is like someone who dresses fashionably but wears no vest.”
—Walter Benjamin (1892–1940)