From: "Mauricio Fernández" Date: 2002-08-24T19:49:30+09:00 Subject: Re: Why Ruby Uses Mark-and-Sweep GC? On Sat, Aug 24, 2002 at 12:39:54PM +0900, Perry E. Metzger wrote: > > Mauricio Fern�ndez writes: > > There's however a problem with bringing generational GC to Ruby. If your > > generations are G0 (newer), G1, ..., when marking objects in G0 you > > have to go through "root variables"� (frames, globals...) AND the > > objects in G1, .., Gn which point to things in G0. > > This is no different from the generational GC problem in most > languages. There are several good monographs on garbage collection out > there that explain how one overcomes such problems in practice. But having an automatically managed remembered list (or equivalent method) only works for code written in Ruby. The programmer must update it manually in modules in C, which is the issue I was talking about: the breakage of most extensions... -- _ _ | |__ __ _| |_ ___ _ __ ___ __ _ _ __ | '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ | |_) | (_| | |_\__ \ | | | | | (_| | | | | |_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_| Running Debian GNU/Linux Sid (unstable) batsman dot geo at yahoo dot com If you really want pure ASCII, save it as text... or browse it with your favorite browser... -- Alexandre Maret