15 Mar
2008
15 Mar
'08
10:01 p.m.
On Sat, 2008-03-15 at 16:58 -0400, MenTaLguY wrote:
My preferred approach would be to replace GObject with NRObject in the SPObject hierarchy, removing the inter-SPObject refcounting (which would create unbreakable GC cycles) and explicit member initialization (no longer needed, as NRObject calls the C++ constructor/destructors). At that point we can start using all C++ features directly in the existing SPObject classes.
Actually, I think it may be best if I move the GC stuff into e.g. a distinct NRGCObject subclass, so that we don't have to do the GC migration things at the same time as everything else.
-mental