From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-09-06 16:42:36
David Abrahams wrote:
> You need to make sure that the GC doesn't trace
> that hashtable. And when strings are reclaimed, you need to make sure
> that entries in that hashtable are invalidated.
> You need to make sure that everything other
> than the big interning hashtable that could reference these strings is
> allocated in traced memory.
Now I understand what you were talking about earlier :-)
I would think the first step is making a "mem.h" header which defines
some alloc/dealloc macros (to match the gc calls) with standard
definitions, getting every other source to include that header, and
replace all instances of allocation/deallocations with the macros.
We can then replace in any memory handling we want globally.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk