Mail Archives: djgpp/1996/05/01/03:26:39
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
>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.
I may be completely Bass-Ackwards, but I thought I read somewhere in the
docs that for performance reasons, the data is not paged out of memory, but
is marked as pageable so if the spawned proccess actually needs that much
memory, it can get it. Am I right?
---
This message may not be transmitted over any network owned directly or
indirectly by Microsoft without a $5000 royalty. Transmission of this message
on such a network implies acceptance of these terms. Subsequent messages
are to be individually licensed.
- Raw text -