On Monday 04 January 2010 at 14:34, Vasily Chekalkin wrote: > chromatic wrote: > > We'd have to detect when it's safe to recycle a CallContext, but we *could* > > hijack its destroy(), let the GC capture a few, and then store them in the > > cache by size and avoid subsequent GC runs. > > It reminds me pre-PMC version of Parrot_Contexts... It's really hard to > make it correct. Refcounting gave us fits there.
If destroy() isn't reliable for figuring out when CallContexts are safe to put back in the cache, we have a bigger problem elsewhere. Refcounting won't be a problem -- or do you see another issue I can't recall now? -- c _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
