=============== Diff against VMMaker-dtl.407 ===============
Item was changed:
----- Method: ContextInterpreter>>snapshotResume:heapSize:swapBytes:oldBaseAddr:specialObjectsOop:lastHash:savedWindowSize:fullScreenFlag:extraVMMemory: (in category 'snapshot utility primitives') -----
snapshotResume: byteArrayOrBitmap heapSize: desiredHeapSize swapBytes: swapBytes oldBaseAddr: oldBaseAddr specialObjectsOop: specialObjects lastHash: hashValue savedWindowSize: windowSize fullScreenFlag: fullScreen extraVMMemory: extraMemory
"Arrange for the interpreter to resume execution from a snapshot of saved
+ memory and interpreter state. The current object memory and interpreter
+ state is discarded, and the interpreter resumes execution at the point of
+ the supplied image snapshot.."
- memory and interpreter state. The current object memory and interpreter state
- will be discarded, and the interpreter will resume execution at the point of the
- supplied image snapshot. Answer the address of the previous object memory
- or nil if this is the first evaluation."
"Notes - The parameters windowSize, fullScreen and extraMemory are currently
not used when resuming the VM in a new image. The display size and fullscreen
mode are probably best set from the image by calling primitiveSetDisplayMode
prior to primitiveResumeFromSnapshot. The extraMemory parameter is ignored
here because we are simply copying the new object memory over a previously
allocated heap space."