Xref: utzoo comp.editors:1249 gnu.emacs:2107 comp.unix.wizards:20055 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!uc!uh!fin From: fin@uh.msc.umn.edu (Craig Finseth) Newsgroups: comp.editors,gnu.emacs,comp.unix.wizards Subject: Re: GNU Emacs, memory usage, releasing Keywords: GNU emacs malloc memory working set gap editor Message-ID: <1059@uc.msc.umn.edu> Date: 8 Jan 90 16:43:41 GMT References: <1558@aber-cs.UUCP> <129799@sun.Eng.Sun.COM> <50359@bbn.COM> Sender: news@uc.msc.umn.edu Reply-To: fin@uh.UUCP (Craig Finseth) Organization: Minnesota Supercomputer Center, Minneapolis, MN Lines: 17 In article peter@ficc.uu.net (Peter da Silva) writes: >There seems to be an assumption here that the only possible methods are >buffer gap and a linked list of lines. What about a linked list of larger >blocks? ... Think of pure buffer gap and linked line as opposite ends of a continuum. (Technically, linked character would be on the one end, but I will ignore that case.) Pure buffer gap has one chunk, which is the entire object. As you divide it into separate chunks (paged buffer gap), the number increases and their size decreases. Eventually, you get to a chunk size of one line and have linked line. In may of the intermediate cases, whether you use an array or linked list is an implementation detail. Craig A. Finseth fin@msc.umn.edu [CAF13] Minnesota Supercomputer Center, Inc. +1 612 624 3375