Um, no. For Qt to do what you claim, it would have to traverse all the application data -- including data owned by non-Qt code -- to discover what application objects are still in use. In other words, it would have to implement a GC.
Unless your definition of "almost exactly the same stuff" is a lot looser than what I would think. Would you care to give an example of which Qt API you mean? And perhaps what binding, if that's relevant? On Jul 26, 4:13 am, DanH <danhi...@ieee.org> wrote: > That's odd, because Qt can do almost exactly the same stuff, without > weak references or implicit garbage collection, using reference chains > that the average user never has to think about. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
