Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site python.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!python!michael
From: michael@python.UUCP (M. Cain)
Newsgroups: net.micro.6809
Subject: Re: Re: C compiler strange errors
Message-ID: <188@python.UUCP>
Date: Mon, 24-Mar-86 13:09:52 EST
Article-I.D.: python.188
Posted: Mon Mar 24 13:09:52 1986
Date-Received: Tue, 25-Mar-86 05:00:14 EST
References: <776@ihwpt.UUCP>
Distribution: net
Organization: Bell Communications Research
Lines: 17

>                Really big arrays would have to be faked
> with alloc() and malloc(), I guess.  Anybody out there
> ever try those and live?
> 
> mike k

I have an editor that uses one of alloc() or malloc() -- I don't
remember which off the top of my head -- to get buffer space as
needed.  My reason was that I occasionally run my Coco multi-user,
with my wife and I both editing small files, and wanted the buffer
size to be "just big enough" to hold the file.  The buffer is in
memory rather than on disk because both the console and the external
terminal are dead while the disk is running.  I've been contemplating
a RAMdisk to alleviate the limited buffer size problem inherent in
my current solution.

Michael Cain