it will issue WARNINGs about the type mismatches. It's not clear
how to make the compiler smart enough to fix this in general, but
a workaround is given in the entry for 117 in the BUGS file.
+* The doc/cmucl/ directory, containing old CMU CL documentation,
+ is no longer part of the base system. The files which used to
+ be in the doc/cmucl/ directory are now available as
+ <ftp://sbcl.sourceforge.net/pub/sbcl/cmucl-docs.tar.bz2>.
+?? lots of tidying up internally: renaming things so that names are
+ more systematic and consistent, converting C macros to inline
+ functions, systematizing indentation
planned incompatible changes in 0.7.x:
* The debugger prompt sequence now goes "5]", "5[2]", "5[3]", etc.
# generated files but other things (e.g. customization files)
# which shouldn't be in the distribution
-rm customize-target-features.lisp
+# It's not unheard of to copy the old CMU CL docs into their
+# traditional sbcl-0.6.x place. If so, it shouldn't end up in
+# the distribution.
+rm -rf doc/cmucl
+
+# miscellaneous other customizations which shouldn't be propagated
+rm -rf customize-target-features.lisp
+
+# Fall through to ordinary cleanup.
sh clean.sh
-SBCL is -- ahem! -- not completely documented at this point.
-What can I say? Help with documentation might not be refused.:-)
-
-There is a user manual in DocBook format, in user-manual.sgml.
-It's based on the CMU CL user manual, and some of its chapters
-aren't done, 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's available from SourceForge
-by anonymous ftp.
+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 DocBook format, in user-manual.sgml. (In
+binary distributions, the compiled-into-HTML translations are also
+included.) Several free software packages are available to compile
+DocBook into HTML or other formats. The commands to use 'jade' to
+translate the manual into HTML are in make-doc.sh.
+
+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)
+or
+ (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
+<ftp://sbcl.sourceforge.net/pub/sbcl/cmucl-docs.tar.bz2>.