Content deleted Content added
clean up, typo(s) fixed: For example → For example, using AWB |
|||
Line 5:
==Disk images==
{{Main article|Disk image}}
If a system has all its state written to a disk, then a system image can be produced by simply copying that disk to a file elsewhere, often with [[disk cloning]] applications. On many systems a complete system image cannot be created by a disk cloning program running within that system because information can be held outside of disks and volatile memory, for example in non-volatile memory like boot ROMs.
Line 16:
===Programming language support===
Some [[programming language]]s provide a command to take a system image of a program. This is normally a standard feature in [[Smalltalk]] (inspired by [http://www.mprove.de/diplom/gui/kay68.html FLEX]) and [[Lisp (programming language)|Lisp]], among other languages. Development in these languages is often quite different from many other programming languages. For example, in Lisp the programmer may load packages or other code into a running Lisp [[implementation]] using the [[read-eval-print loop]], which usually compiles the programs. Data is loaded into the running Lisp system. The programmer may then [[ROM image|dump]] a system image, containing that pre-compiled and possibly customized code - and also all loaded application data.
<!--
It's to avoid the time penalty of recompiling that software like Emacs use images, and modern Common Lisp interpreters, anyway, compile packages as a matter of course (See SBCL, CMUCL, etc.)
| |||