Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: William Harold Newman <wnewman@us...> - 2002-10-02 23:22:51
Update of /cvsroot/sbcl/sbcl/src/code
In directory usw-pr-cvs1:/tmp/cvs-serv2243/src/code
added build id to .core files to try to discourage .core/sbcl
RCS file: /cvsroot/sbcl/sbcl/src/code/save.lisp,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- save.lisp 16 Jan 2002 23:54:29 -0000 1.16
+++ save.lisp 2 Oct 2002 23:22:47 -0000 1.17
@@ -32,11 +32,20 @@
- "Saves a CMU Common Lisp core image in the file of the specified name,
- killing the current Lisp invocation in the process (unless it bails
- out early because of some argument error or something).
+ "Save a \"core image\", i.e. enough information to restart a Lisp
+ process later in the same state, in the file of the specified name.
- The following &KEY args are defined:
+ This implementation is not as polished and painless as you might like:
+ * It corrupts the current Lisp image enough that the current process
+ needs to be killed afterwards.
+ * There is absolutely no binary compatibility of core images between
+ different runtime support programs. Even runtimes built from the same
+ sources at different times are treated as incompatible for this purpose.
+ This isn't because we like it this way, but just because there don't
+ seem to be good quick fixes for either limitation and no one has been
+ sufficiently motivated to do lengthy fixes.
+ The following &KEY arguments are defined:
The function to run when the created core file is resumed.
The default function handles command line toplevel option