From:	Tudor <tudor AT cam DOT org>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: windows <-> cwsdpmi
Date:	Thu, 26 Dec 1996 18:43:48 -0800
Organization:	Communications Accesibles Montreal
Lines:	33
Message-ID:	<32C337E4.5C90@cam.org>
References:	<851364688 DOT 618879 DOT 0 AT abwillms DOT demon DOT co DOT uk>
Reply-To:	tudor AT cam DOT org
NNTP-Posting-Host:	dynappp-38.hip.cam.org
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Alaric B. Williams wrote:
 
>> Yup, but sadly I don't have the URL for it anymore :-)
I read about a C/C++ garbage collector in a BYTE magasine.It(the GC) was
availeble from the BYTE web site.I don't know if it is there anymore coz
the BYTE I read is kinda old(1 year or so)...Maybe if they have
archives...?
 
>> Tada! It's called conservative GC because if anything - maybe not
>> even a pointer - seems to refer to a block, it stays. Therefore, some
>> blocks hang around longer than they need to. But we've got to be real
>> sure in a non-typesafe C program.
The GC I read about had the same problem:anything that had a pointer to
itself stayed,so a circular list really busted the GC :
........
void *a,*b,*c;
a=&b;
b=&c;
c=&a;
......
at this point,even if the three pointers aren't used anymore they stay
because each of them is being pointed at(a circular list).

-- 
tudor 'at' cam 'dot' org
http://www.cam.org/~tudor

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS d-(--) s(-):(+) a? C+ UL>++++ P L>+++++ E- W++ N o K---(----) w---
O---- M-- V-? PS+++ PE Y PGP t+ 5-- X+++>++++ R tv b+ DI D+ G e->++
h>++ r- y>+++++ 
------END GEEK CODE BLOCK------

- Raw text -