>This thread and particularly the following passage:
>
> "If I understand this right, you're suggesting essentially dumping
> out part of the Haskell heap to a file."
>
>reminds me very strongly of APL, where dumping the current state of
>the system into a binary file that you can later reload (and resume
>your work where you left it) has always been a possibility. This was
>useful not just for interactive work but also for breaking down large
>computations and escape the reaper built into the mainframe's batch
>queue :) Is it anything of the kind that Runciman is working on or
>something less ambitious?
>
This has well know disadvantages. Simon has already pointed out that it's
not relocatable. It's also limited to the size of virtual memory and takes
up that amount of space even though most of it may not be used. Loading a
complete persistent memory at once is overkill. You should load it's
objects lazily and only store away accessible stuff at commit time.
Tony Davie, Computer Science, St.Andrews University, North Haugh, St.Andrews
Scotland, KY16 9SS, Tel: +44 1334 463257, Fax: +44 1334
463278
mailto:[EMAIL PROTECTED] Home: http://www.dcs.st-and.ac.uk/~ad/Home.html
Handel Index and Chronology:
http://bruichladdich.dcs.st-and.ac.uk/HandelWWW/HandelCat.html
Limerick Archive:
http://bruichladdich.dcs.st-and.ac.uk/LimericksDir/Limericks.html
'There is magic in the web' - Othello, Act 3, Scene 4
