the protect is used to "protect" data set by pAllocCreate if the new object is later initialized with a type specific object-initialization … More...
#include <LibMkKernel_mk.h>
Data Fields | |
bool | isLocal |
has the object a local reference? - has been created by TLS or MkBufferCreateREF ? … | |
MK_OBJ | prev |
previous | |
MK_OBJ | next |
next | |
the protect is used to "protect" data set by pAllocCreate if the new object is later initialized with a type specific object-initialization …
Definition at line 3092 of file LibMkKernel_mk.h.
bool MkObjectProtectS::isLocal |
has the object a local reference? - has been created by TLS or MkBufferCreateREF ? …
In theory a "local" object in undeleteable but still useable linke a "global" object. This is usefull if the "local" object act like a cache, provide an "working" object without requirement to create the "working" object again if required multiple times.
The difference between a "global" object and a "local" object is the refCount, the refCount of a "local" object is always initialized with 1 and should never be < 1.
Definition at line 3103 of file LibMkKernel_mk.h.
MK_OBJ MkObjectProtectS::next |
next
Definition at line 3106 of file LibMkKernel_mk.h.
MK_OBJ MkObjectProtectS::prev |
previous
Definition at line 3105 of file LibMkKernel_mk.h.