Editing Object lifetime (section)

==Determinism==

Creation of an object is generally ''deterministic'', but destruction varies by programming context. Some contexts allow for deterministic destruction, but some do not. Notably, in a garbage-collection environment, objects are destroyed when the garbage collector chooses.

The syntax for creation and destruction varies by programming context. In many contexts, including C++, C# and Java, an object is created via special syntax like <code>new ''typename()''</code>. In C++, that provides [[manual memory management]], an object is destroyed via the <code>delete</code> keyword. In C# and Java, with no explicit destruction syntax, the garbage collector destroys unused objects automatically and non-deterministically.

An alternative and deterministic approach to automatic destruction is where the object is destroyed when code decrements the object's [[reference count]] to zero.

With an [[object pool]], where objects may be created ahead of time and reused, the apparent creation and destruction of an object may not correspond to actual. The pool provides reinitialization for creation and finalization for destruction. Both creation and destruction may be non-deterministic.

Objects with [[static memory allocation]] have a lifetime that coincides with the [[execution (computing)|run]] of a program, but the ''order'' of creation and destruction of the various static objects is generally non-deterministic.