DeleteObject

DeleteObject

DeleteObject, DeleteObject(pattern)

Stack

Stack		Description
Stack(In)		persistent/transient object
Stack(Out)		-

The object is

• marked with one bit as logically deleted
• removed from all known Root-EP-Collections (see DeregisterObject)
• in the garbage collection of its class.

The operation is inverse to CreatePersObject / CreateTransObject(,KEEP), i.e. from the collections in which it was entered by CreatePersObject it is removed by DeleteObject. To avoid that many collections are searched in vain, DeleteObject also depends on the settings made with SetLayer, SetDomain(WRITE) and SetPattern.
The following example shows the connection between layer, domain and Bitpattern for Inheritance as well as the following code example.

Transient objects are logically deleted by DeleteObject and then logged on to the garbage collection(CX_GARBAGE_MANAGER։։Register), so that the object is deleted as soon as it is no longer referenced by any variable.

An object deleted with DeleteObject can be reactivated with UndeleteObject. For transient objects, only the logical deletion status is reset, the object is not logged off again from the garbage collection.

An object can be queried by means of the function CX_SIMPLE::Deleted() whether it is (logically) deleted or not.

See also:

• KillObject
• CreateTransObject(,KEEP)