Message-Id:	<199704281117.NAA23916@grendel.sylaba.poznan.pl>
Comments:	Authenticated sender is <grendel@[150.254.113.14]>
From:	"Mark Habersack" <grendel AT hoth DOT amu DOT edu DOT pl>
Organization:	PPP (Pesticide Powered Pumpkins)
To:	alaric AT abwillms DOT demon DOT co DOT uk
Date:	Mon, 28 Apr 1997 13:17:04 +0100
MIME-Version:	1.0
Subject:	Re: Usage of directory entries
Reply-to:	grendel AT hoth DOT amu DOT edu DOT pl
CC:	Matthias DOT Paul AT post DOT rwth-aachen DOT de, opendos-developer AT delorie DOT com
References:	<199704251241 DOT OAA11865 AT grendel DOT sylaba DOT poznan DOT pl>
In-reply-to:	<862047724.1010371.0@abwillms.demon.co.uk>

Once upon a time (on 26 Apr 97 at 10:45) Alaric B. Williams said:

> On 25 Apr 97 at 14:41, Mark Habersack wrote:
> 
> > > A garbage collector is a process that deallocates memory automatically.
> > > With
> [...]
> > mmm... sounds sensible. Do you know of any GC already working somewhere?
> 
> Erm... there are zillions! Look on the web for Hans Boehm's GC for C. It's
> about as good as GC can get under C. Languages with "real" pointers do
> better from it.
I meant some GC for an *operating system", not for a single application. Even 
Borland has such one! ;-)

> > And what about the 'flexible' swapfiles - they out of definition cannot be
> > stored in solid blocks?
> 
> In which case, treat them like any other file, just as eligible for
> defragmentation.
Right.
==================================================
Stand straight, look me in the eye and say goodbye
Stand straight, we drifted past the point of
  reasons why.
Yesterday starts tommorow, tommorow starts today
And the problems seem to be we're picking up the
  pieces of a ricochet...

- Raw text -