Mon, 05 May 1997 11:29:52 -0700
> > As I've said, Allegro Common Lisp has a "dumplisp" command that saves
> > an entire lisp process, which can be started back up.
> > So you develop your code, and do a dumplisp to save all the objects.
> > Because Lisp allows dynamic redefinition, if you change your code,
> > you just *change the code*, and now your process has the new code.
> > It's not like C, there is not recompile & relink & rerun development cycle!
> Practically speaking, how do you browse and debug code written using
> this methodology? Does ACL save the formatted source for each definition?
Practically speaking, you'd have to start using source code in files,
and use the emacs<->lisp interface. This would be how to do it
until the object-based module system is built, which is very high on my list.
The created CLOS objects would continue to exist only in the process image.
You can "checkpoint" your development by doing dumplisp's once in a
while, just like you write out buffers in an editor.
If you do something that crashes the system (rare if not doing
low-level stuff) you can restart with anearlier saved process.