On 17 Feb 2014, at 13:33, Mathias Bauer <[email protected]> wrote:
> in case somebody else is also interested in this: it seems that Apple's > runtime "protects" the developer by ignoring changes to the retain count as > soon as the object entered its deallocate method. Wrong decision, IMHO. It is likely that this is a side effect of weak reference support. Classes must notify the runtime when they start deallocation now, so that concurrent loads of weak references abort the deallocation. Apple's implementation stores objects' refcounts in a map table, so once the object has entered deallocation it's likely just a separate path. I wouldn't be surprised if this is not an active decision at all, however it does make adding cycle detection to ARC easier... David _______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
