Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site unisoft.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!lll-crg!lll-lcc!unisoft!fnf
From: fnf@unisoft.UUCP (Fred Fish)
Newsgroups: net.emacs
Subject: Re: Gnu use of alloca and setjmp
Message-ID: <6@unisoft.UUCP>
Date: Wed, 15-Jan-86 20:10:55 EST
Article-I.D.: unisoft.6
Posted: Wed Jan 15 20:10:55 1986
Date-Received: Fri, 17-Jan-86 06:35:58 EST
References: <578@harvard.UUCP> <5140001@acf4.UUCP> <145@newton.ARPA> <438@well.UUCP> <415@newton.ARPA>
Reply-To: fnf@unisoft.UUCP (Fred Fish)
Organization: UniSoft Systems; Berkeley, CA
Lines: 18

In article <415@newton.ARPA> crl@newton.UUCP (LaBrec) writes:
>In article <438@well.UUCP> fnf@well.UUCP (Fred Fish) writes:
>>     ...        GNU emacs basically shoves things into text space by
>>extending it to overlap part of the data space.  If you have a 4Mb
>>"hole" between text and data, you end up with a VERY large shared 
>>text program!
>
>And if your system is demand-paged (what system that GNU EMACS runs on 
>isn't?), then the hole is never paged in, so, no lossage to the system.

My original posting still stands.  Since I see no "smiley-face" on yours,
I have to assume that you are not aware that there are other systems
in the real world that are not demand-paged.  GNU emacs runs quite
nicely on UniSoft's SVR2 (swapping) port for the 68000 and 68010.  There
is nothing in GNU emacs that requires it to be running on a demand-paged
system (though it certainly helps).

-Fred