Date: Fri, 26 Apr 1996 11:47:14 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Orlando Andico <orly AT abigail DOT eee DOT upd DOT edu DOT ph>
Cc: Marcelo Cantos <mcantos AT ocean DOT com DOT au>, djgpp AT delorie DOT com
Subject: Re: Error messages and warnings...
In-Reply-To: <Pine.LNX.3.91.960425223440.1663D-100000@abigail.eee.upd.edu.ph>
Message-Id: <Pine.SUN.3.91.960426114417.26200N-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Thu, 25 Apr 1996, Orlando Andico wrote:

> > Only if by ``space'' you mean disk space.  If you mean the RAM, then the 
> > size of the program is not important, because the DPMI host will swap the 
> > editor (or a part thereof) out to make enough space for the compiler.
> 
> Actually I meant both... don't tell me that Emacs with its bloated binary 
> consumes less space than Jed... of course Jed can be a memory hog too 
> since it's a DJGPP-compiled program. But (unless I'm way off, correct me 
> if I'm wrong) a smaller binary means that much less memory consumed. 
> Which then translates to more memory for the compiler.

Wrong.  When you invoke the compiler from within Jed or Emacs, the DPMI 
server (Windows, CWSDPMI or anything else) will swap out the editor to 
disk to make space for the compiler.  So except for the swap itself, the 
compiler will have the same amount of memory under both editors.