From: Panayotis K. <pan...@pa...> - 2011-01-21 19:40:21
|
On Jan 21, 2011, at 6:31 PM, Arno Puder wrote: > he Objective-C backend still relies on > reference counting and it happens *very* quickly that your application > contains a cycle in the data structure and therefore leaks memory. These > are just two things where the new backend is superior. I have a question with the GC. There are some selectors in iOS which return an autoreleased object. This is not really the problem. The problem is if this object is released later on, for example after an animation cycle. I can't think right now of a working test example, but I'd like to hear how well the GC behaves in such mixed situations. Right now, what I do with the ObjC backend is to manually retain this object and release it when I know that I don't need it anymore. (and I think this is not a bug of ObjC, it is the way these asynchronous object manipulation works) |