Topic: save-restore

Summary

When control is temporarily passed to a new object, the current state must be saved for later restoring. This can be the program counter for sub-routine calls, or a local environment for backtrack saves. In a workspace oriented system, external medium save/restore preserves objects between and during user sessions. The most common save-restore medium is a push-down stack used for embedded contexts. (cbb 5/80)

Subtopic: state save

QuoteRef: cbb_1973 ;;3/19/74 state save is required only if want to retain control over the long run

Subtopic: save/restore of objects

QuoteRef: radiG1_1965 ;;13 external medium Save (object-list, optional-tag) and restore (object-list, optional-tag), indexed by name, tag. duplicate names are pushed

Subtopic: save/restore stack

QuoteRef: sammJE_1969 ;;404 save and restore push-down operations used a lot

Subtopic: call/return

Quote: always keep the powers-of-two table and the routine changing sequence (PERM) in memory; the later simplifies call and return from a routine [»turiA3_1951]

Related Topics

Group: function   (12 topics, 232 quotes)
Topic: continuation (16 items)
Topic: persistent data structure (37 items)
Topic: return from procedure (9 items)
Topic: running programs in a workspace or environment (14 items)
Topic: stacks
(6 items)