From: William Harold Newman Date: Fri, 10 Aug 2001 14:43:17 +0000 (+0000) Subject: 0.pre7.8: X-Git-Url: http://repo.macrolet.net/gitweb/?a=commitdiff_plain;h=8dc064d2296902f01afd9107e89a81146e3771fe;p=sbcl.git 0.pre7.8: (The old CMU CL documentation is now available from .) tweaked docs/.cvsignore so that if you like keeping the old CMU CL documentation in the old place, CVS doesn't pester you about it --- diff --git a/NEWS b/NEWS index 1a3a1bf..38ff4a8 100644 --- a/NEWS +++ b/NEWS @@ -823,6 +823,13 @@ changes in sbcl-0.7.0 relative to sbcl-0.6.13: 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 + . +?? 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. diff --git a/distclean.sh b/distclean.sh index 9ba8508..33034f9 100644 --- a/distclean.sh +++ b/distclean.sh @@ -4,5 +4,13 @@ # 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 diff --git a/doc/.cvsignore b/doc/.cvsignore index cfbc1ef..43e9737 100644 --- a/doc/.cvsignore +++ b/doc/.cvsignore @@ -1 +1,2 @@ -*.htm \ No newline at end of file +*.htm +cmucl diff --git a/doc/README b/doc/README index bfb2f08..375689d 100644 --- a/doc/README +++ b/doc/README @@ -1,12 +1,25 @@ -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 +. diff --git a/version.lisp-expr b/version.lisp-expr index 1103bab..bfb8e16 100644 --- a/version.lisp-expr +++ b/version.lisp-expr @@ -16,4 +16,4 @@ ;;; four numeric fields, is used for versions which aren't released ;;; but correspond only to CVS tags or snapshots. -"0.pre7.7" +"0.pre7.8"