As I understand it the [weak] attribute (new for win32 in 10.1 Berlin) ensures there is no ref counting on interface variables AND that the variable is cleared (set to nil) when the object implemeting the interfaces is destroyed.
As I understand it the [weak] attribute (new for win32 in 10.1 Berlin) ensures there is no ref counting on interface variables AND that the variable is cleared (set to nil) when the object implemeting the interfaces is destroyed.
However, does anyone know if this "clearing" is thread safe? I.e. if the object implementing the interface, the weak variable is pointing to is destroyed, is clearing the week variable an "atomic" operation?
However, does anyone know if this "clearing" is thread safe? I.e. if the object implementing the interface, the weak variable is pointing to is destroyed, is clearing the week variable an "atomic" operation?
ReplyDelete/sub
Yes, it is thread safe.
ReplyDeletewhen ref counting is involved, the counter needs to be inc/decremented atomically
ReplyDelete