Path: utzoo!attcan!uunet!mailrus!iuvax!ux1.cso.uiuc.edu!midway!msuinfo!frith!dailey
From: dailey@frith.uucp (Chris Dailey)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Files larger than available memory.
Message-ID: <1990Sep24.150432.25049@msuinfo.cl.msu.edu>
Date: 24 Sep 90 15:04:32 GMT
References: <924@ucsvc.ucs.unimelb.edu.au> <1990Sep23.174736.16118@lavaca.uh.edu>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University
Lines: 21

In article <1990Sep23.174736.16118@lavaca.uh.edu> jet@karazm.math.uh.edu (J. Eric Townsend) writes:
>It can be done.  It's somewhat bizarre, but it can be done.  Essentially,
>you keep track of the changes to the file.  You change the file whenever
>you reach one of a set of conditions:
>-- size of changes > some default size
>-- user is not doing anything (cycle stealing, of a sort :-)
>-- user goes forward or backwards in the file some distance > x

>Any questions?

Why, yes.  What if the text to be inserted is greater than the space on
the disk?  There is no super-elegant way of doing this.  You'd have to
allocate more disk space, link it in.  Sounds like a lot of
system-dependent stuff to me.

>J. Eric Townsend -- University of Houston Dept. of Mathematics (713) 749-2120
--
Chris Dailey   dailey@(cpsin.cps|frith.egr).msu.edu
"Rise again, rise again/Though your heart it be broken and life about to
end./No matter what you've lost, be it a home, a love, a friend,/
Like the Mary Ellen Carter, rise again!" -- a song by the late Stan Rogers