the byte fasl file version is now equal to the ordinary
fasl file version.
+changes in sbcl-0.7.0 relative to sbcl-0.6.13:
+* There are new compiler optimizations for various functions: FIND,
+ POSITION, FIND-IF, POSITION-IF, FILL, COERCE, TRUNCATE, FLOOR, and
+ CEILING. Mostly these should be transparent, but there's one
+ potentially-annoying problem (bug 117): when the compiler inline
+ expands the FIND/POSITION family of functions and does type
+ analysis on the result, it can find control paths which have
+ type mismatches, and when it can't prove that they're not taken,
+ 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>.
+* The default value of *BYTES-CONSED-BETWEEN-GCS* has been
+ doubled, to 4 million. (If your application spends a lot of time
+ GCing and you have a lot of RAM, you might want to experiment with
+ increasing it even more.)
+?? The system's handling of top-level forms and EVAL-WHEN is now
+ more ANSI-compliant, fixing bugs
+ ?? IR1-3 and
+ ?? IR1-3a.
+ It's also done by much newer code, so there might be some new bugs,
+ but hopefully if so they'll be less fundamental and more fixable.
+?? 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.
as you get deeper into recursive calls to the debugger command loop,