Re: Memory allocation overhead

> I just saw that in your last check-in you used MEMORY.free.
> This is a bad idea in my opinion. And it won't help anyway 
> when using gec+boehm (it's currently implemented as a no-op).

And this is actually very dangerous because even if you think there are no
references to the object, the generated C code might still have a reference
or two. So at the next GC cycle it could basically cause a problem (be a
segmentation violation or something else). I'm not sure why it was added in
MEMORY at the first place, but I would not use it.

Manu


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace