[gclist] why malloc/free instead of GC?

Enrico Weigelt weigelt@metux.de
Tue, 18 Feb 2003 20:28:03 +0100

On Tue, Feb 18, 2003 at 01:58:07PM -0500, Igor Pechtchanski wrote:

> Same way generational GC copes with it, i.e., through write barriers.
> However, when I said "separate entities", I meant mostly "independent
> heaps", in which case there won't be any cross-references.
Ok, so the programmer has to make sure, that these two pools are 
strictly separate. hmm. 
This is almost the same like the pooled allocator of the apache2.

 Enrico Weigelt    ==   metux ITS 
 Webhosting ab 5 EUR/Monat.          UUCP, rawIP und vieles mehr.

 phone:     +49 36207 519931         www:       http://www.metux.de/     
 fax:       +49 36207 519932         email:     contact@metux.de
 cellphone: +49 174 7066481	     smsgate:   sms.weigelt@metux.de
 Diese Mail wurde mit UUCP versandt.      http://www.metux.de/uucp/