[gclist] why malloc/free instead of GC?

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

On Tue, Feb 18, 2003 at 07:44:31PM +0000, rog@vitanuova.com wrote:
> > a) strings (and other objects which contain no pointers)
> > b) typed objects (we only have to know where pointers lay around)
> > c) untyped objects (must be treatened as an array of pointers)
> pointers between b) and c) are gonna cause problems.
why should they ? 

i dont wanna build an allocator with strictly separated heaps.
the different heaps are for easy detection of the best scan method.
you can simply guess on the address, whether the object is typed,
untyped or w/o pointers.

 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/