>>>> "Andy" == Andy Piper
<andy(a)xemacs.org> writes:
Andy> At 10:19 AM 8/19/99 +0200, Michael Sperber [Mr. Preprocessor] wrote:
>>>>>> "mt" == Marcus Thiessel
<marcus(a)xemacs.org> writes:
>
mt> SL Baur writes:
>
>>> I now suspect dumping. I hate dumping, I hate it, I hate it, I hate
>>> it, I hate it. Why must we do something so stupid?
>
mt> The question is what are the alternatives? Are there any at all?
>
> Absolutely. I don't know about Kyle's and Olivier's plans in details,
> but as long as you have precise memory management (hint, hint ...) you
> can just dump out a heap image and mmap it back in. This can even be
> done in such a way as to create architecture-independent heap images.
> I wrote code to do that for Scheme 48 which should show up in one of
> the next releases.
Andy> I personally don't like this solution. It assumes you have mmap and surely
Andy> also has the problem that native windows suffers from that the memory has
Andy> to be mapped back in at a specific address. This causes dll conflicts in
Andy> windows.
Neither is true. The worst that can happen is that you actually have
to read the heap image, which means that this portion of memory
(unless there's something other than mmap which allows you to fiddle
with the pager) cannot be shared between concurrent invocations of
XEmacs. Also, as long as you have precise memory management, you can
relocate.
--
Cheers =8-} Chipsy
Friede, Völkerverständigung und überhaupt blabla