> BTW is there a document somewhere that summarizes the run-time costs > of inheriting from GCObject etc, or should I just look at the source?
GCObject has an inlined empty constructor, and no destructor. GCFinalizeableObject does have a virtual empty destructor. So the cost is nothing. What does cost though is that allocation is now done through MMgc functions that are probably slightly slower than simply malloc/free is. Additionally these functions null out the area before returning it, though I'm not entirely sure why it does this, but a guess is that this way it's less likely that the conservative GC will find bogus edges. / Jonas _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
