Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!i.cc.purdue.edu!j.cc.purdue.edu!nwd
From: nwd@j.cc.purdue.edu (Daniel Lawrence)
Newsgroups: comp.sys.atari.st
Subject: Re: More about MicroEmacs 3.9 1/4
Summary: uEMACS
Keywords: uEMACS memory
Message-ID: <8627@j.cc.purdue.edu>
Date: 3 Jan 89 13:35:45 GMT
References: <2086@van-bc.UUCP> <2089@van-bc.UUCP>
Reply-To: nwd@j.cc.purdue.edu (Daniel Lawrence)
Organization: Purdue University
Lines: 16

In article <2089@van-bc.UUCP> rthurlow@van-bc.UUCP (Rob Thurlow) writes:
>Well, I have a few more observations about MicroEmacs 3.9-and-a-quarter.
	<he goes on to describe some memory fragmentation
		and usage problems....>

	MicroEMACS was allocating line structures only in 16 byte
increments.  This was very good for editing, not so good on storage.
By allocating only the needed # of bytes when the file is first read
in, and then allocating in 16 byte chunks when you first add a char
to a line, I seem to get the best of both worlds... an apox 30%
decrease in RAM usage.  Look for this in the upcomming 3.10 release.

					Daniel Lawrence
					(317) 742-5153 nwd@j.cc.purdue.edu
					The Programmer's Room Fido 1:201/10
					(317) 742-5533