SBCL 1.0.34 released

Hi,

I've just tagged and released sbcl-1.0.34.  Apart from a report of an
issue with RUN-PROGRAM on FreeBSD/x86-64, no burning issues were
reported during the freeze period (as it were); that said, it was and is
the festive season, so it is possible that testing was lighter than
usual.

Happy New Year,

Christophe

changes in sbcl-1.0.34 relative to sbcl-1.0.33:
  * minor incompatible change: threading support is now enabled by default
    on x86[-64] Linux.
  * enhancement: SB-INTROSPECT:DEFTYPE-LAMBDA-LIST now also works on most
    builtin types.
  * enhancement: Errors during compile-time-too processing (i.e. EVAL-WHEN)
    are now caught and reported just like errors during macroexpansion.
  * enhancement: SB-POSIX now provides access to tcdrain(), tcflow(),
    tcflush(), tcgetsid(), and tcsendbreak(). (thanks to Jerry James)
  * enhancement: ASDF systems can now depends on SB-QUEUE.
  * fixes and improvements related to Unicode and external formats:
    ** bug fix: error handling and restart usage in the ucs-2 external format 
       has been improved.
    ** there is now an implementation of the ucs-4 external format.
    ** the utf-16 and utf-32 external formats are supported.
  * bug fix: SB-POSIX wrapper for putenv no longer tries to put lisp strings
    in the environment. setenv() and unsetenv() are also provided. (reported by
    Fare Rideau; launchpad bug lp#460455)
  * bug fix: LOAD of both .fasl and .FASL type files now forces fasl-style
    loading. This ensures sensible errors for .FASL files from other
    implementations on case-insensitive filesystems. (reported by Willem
    Broekema; launchpad bug lp#489417)
  * bug fix: #p"\\\\" can now be read without error on Win32.  (reported by
    Willem Broekema; launchpad bug lp#489698).
  * bug fix: some minor code rearrangements to reenable warning-free building
    from CMUCL (reported by [email protected]; launchpad bug lp#491104)
  * bug fix: PRINT-OBJECT for clos instances respects the right margin when
    pretty printing
  * bug fix: FIND-PACKAGE & DEFPACKAGE were not thread safe. (reported by
    Attila Lendvai)


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev