Re: Garbage collection (Nick Maclaren)
4 Aug 2004 02:42:49 -0400

          From comp.compilers

Related articles
garbage collection (Lex Spoon) (2003-07-13)
Garbage collection (2004-07-28)
Re: Garbage collection (2004-08-04)
Re: Garbage collection (Sebastian) (2004-08-04)
Re: Garbage collection (2004-08-05)
Re: Garbage collection (Basile Starynkevitch \[news\]) (2004-08-05)
Re: Garbage collection (Nick Roberts) (2004-08-09)
Re: Garbage collection (2004-08-10)
Re: Garbage collection (glen herrmannsfeldt) (2004-08-11)
[16 later articles]
| List of all articles for this month |

From: (Nick Maclaren)
Newsgroups: comp.compilers
Date: 4 Aug 2004 02:42:49 -0400
Organization: University of Cambridge, England
References: 04-07-085
Keywords: GC
Posted-Date: 04 Aug 2004 02:42:48 EDT (William McCabe) writes:
|> I am in the process of writing my own programming language and I would
|> like to use garbage collection as a means for automatic memory
|> management. I have decided that I want to implement a two-stage
|> generational copying collector.
|> I know how a copying and generational collector works but Im not sure
|> how they work when put together. In my mind, generational is similar
|> to coping in being that they both seperate the heap into two
|> semi-spaces, but use totaly different methods to collect garbage. Can
|> someone shield some light on this subject for me.
|> [You might want to ask this on the GC list that spun off from
|> comp.compilers some time ago. -John]

You might also want to start off by deciding what properties you
want your language to have (e.g. its target area), and therefore
what properties you want your garbage collector to have. No
single garbage collector will be appropriate (or even work) for
all requirements.

Nick Maclaren.

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.