Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
All its source-ey goodness is available from SourceForge CVS service
or File Releases web page. Use it wisely.
from the NEWS file in the distribution:
changes in sbcl-1.0.4 relative to sbcl-1.0.3:
* new platform: experimental support for x86-64/darwin (MacOS).
* incompatible change: the thread-safe (on most platforms) getaddrinfo
and getnameinfo sockets functions are used instead of gethostbyaddr
and gethostbyname, on platforms where the newer functions are available.
As a result, the ALIASES field of HOST-ENT will always be NIL on these
* change: runtimes with embedded cores (i.e. saved with :EXECUTABLE T)
don't print the startup banner, but behave as if --noinform was passed
as a command line argument. (thanks to Kevin Reid)
* new experimental feature: added JOIN-THREAD (by NIIMI Satoshi)
* optimization: code using alien values with undeclared types is much faster.
* optimization: the compiler is now able to open code SEARCH in more cases.
* optimization: more compact typechecks on x86-64 (thanks to Lutz Euler)
* bug fix: using standardized COMMON-LISP special variables as loop
variables no longer signals bogus package lock violations. (reported
by Eric Marsden)
* bug fix: declaring local loop variables to be of a range-limited type
such as (SINGLE-FLOAT 1.0 2.0) no longer causes a compile-time error.
(reported by Andras Simon)
* bug fix: >= and <= gave wrong results when used with NaNs. (Some NaN
bugs remain on x86-64.)
* bug fix: the #= and ## reader macros now interact reasonably with
* bug fix: type-checks for function arguments were compiled using the
compiler policy settings of the wrong lexical environment (in 1.0.2
* bug fix: SHADOW accepts characters as string designators, as required
by the spec (thanks to Eric Marsden)
* bug fix: fixed GC safety issues when foreign functions are called with
non-base strings as arguments
* bug fix: more consistent error output for fatal-compiler-warnings, like
* bug fix: functions with proper names were showing up as NIL in
backtraces (reported by Edi Weitz, regression in 1.0.2)
William Harold Newman <william.newman@...>
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C B9 25 FB EE E0 C3 E5 7C
We reject Kings, princes, and voting. We believe in rough consensus
and running code. --- Dave Clark (IETF), 1992