Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


Tree [efb148] sbcl_0_9_18 / doc /

File Date Author Commit
internals 2006-10-09 Christophe Rhodes Christophe Rhodes [5775bb]
internals-notes 2006-08-28 Nikodemus Siivola Nikodemus Siivola [888e04] clean up some unused symbols from SB-EXT
manual 2006-09-13 Juho Snellman Juho Snellman [970dd2]
.cvsignore 2003-11-26 William Harold Newman William Harold Newman [d1b347]
FOR-CMUCL-DEVELOPERS 2000-09-18 William Harold Newman William Harold Newman [a530bb] Initial revision
README 2004-10-28 Christophe Rhodes Christophe Rhodes [10047f]
clean.sh 2004-10-28 Christophe Rhodes Christophe Rhodes [10047f]
entities.inc 2003-11-26 Kevin Rosenberg Kevin Rosenberg [3c5c2c]
make-doc.sh 2004-10-28 Christophe Rhodes Christophe Rhodes [10047f]
sbcl-asdf-install.1 2005-08-03 Juho Snellman Juho Snellman [58d2fc]
sbcl.1 2006-04-05 Rudi Schlatte Rudi Schlatte [2365c1]

Read Me

SBCL is -- ahem! -- not completely documented at this point. What can
I say? Help with documentation might not be refused.:-)

There is a Unix man page, sbcl.1.

There is a user manual in texinfo format, in doc/manual/. (In
binary distributions, the compiled-into-HTML translations are also

Much of the documentation for supported extensions is in their Lisp
doc strings. For example, to find out how to use the SAVE-LISP-AND-DIE
function in the SB-EXT package, you can execute
  (documentation 'sb-ext:save-lisp-and-die 'function)
  (describe 'sb-ext:save-lisp-and-die)
in SBCL.

The user manual is incomplete, and some of its chapters are just notes
that "this is similar to chapter such-and-such of the CMU CL user
manual". The old CMU CL documentation can still be useful both for
missing chapters of the user manual and for documentation of the
internals of the system. It can be downloaded from