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...> - 2003-04-14 01:42:35
Update of /cvsroot/sbcl/sbcl/doc
In directory sc8-pr-cvs1:/tmp/cvs-serv12247
Do EVAL of one --eval form before READ of the next --eval form.
(to avoid package gotchas reported by dan_b)
RCS file: /cvsroot/sbcl/sbcl/doc/sbcl.1,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -d -r1.28 -r1.29
--- sbcl.1 23 Feb 2003 16:14:47 -0000 1.28
+++ sbcl.1 14 Apr 2003 01:42:32 -0000 1.29
@@ -309,9 +309,9 @@
.B --eval <command>
After executing any initialization file, but before starting the
-read-eval-print loop on standard input, evaluate the command given.
-More than one --eval option can be used, and all will be executed, in
-the order they appear on the command line.
+read-eval-print loop on standard input, read and evaluate the command
+given. More than one --eval option can be used, and all will be read
+and executed, in the order they appear on the command line.
.B --load <filename>
This is equivalent to --eval '(load "<filename>")'. The special
@@ -344,10 +344,10 @@
Regardless of the order in which --sysinit, --userinit, and --eval
options appear on the command line, the sysinit file, if it exists, is
loaded first; then the userinit file, if it exists, is loaded; then
-any --eval commands are executed in sequence; then the read-eval-print
-loop is started on standard input. At any step, error conditions or
-commands such as SB-EXT:QUIT can cause execution to be terminated
-before proceeding to subsequent steps.
+any --eval commands are read and executed in sequence; then the
+read-eval-print loop is started on standard input. At any step, error
+conditions or commands such as SB-EXT:QUIT can cause execution to be
+terminated before proceeding to subsequent steps.
Note that when running SBCL with the --core option, using a core file
created by a user call to the SB-EXT:SAVE-LISP-AND-DIE, the toplevel