<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.lisp.steel-bank.devel">
    <title>gmane.lisp.steel-bank.devel</title>
    <link>http://blog.gmane.org/gmane.lisp.steel-bank.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11790"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11782"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11781"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11779"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11778"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11773"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11770"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11769"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11757"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11756"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11754"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11749"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11747"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11739"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11734"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11733"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11723"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11721"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11718"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11712"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11790">
    <title>Compile on Linux (Ubuntu Gutsy)</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11790</link>
    <description>Hi!

When trying to compile sbcl 1.0.19 on a x86-Ubuntu machine (Gutsy) using clisp 2.33.2 as the bootstrap system I run into problems. The binary sbcl version in Ubuntu itself causes our underlying Xen kernel to
panick.  

My hope was that a  self-compiled version might do better. Unfortunately, the build fails with the following stack trace:

***************

498
837
962
976
977
981
982
1008
1009
1012
1013
7835
8126
8486
8490
8491
7897

** - Continuable Error
EVAL: undefined function HOST-CLOAD-STEM
Retry

** - Continuable Error
EVAL: undefined function SB!VM:GENESIS
Retry
deleted #P"/tmp/sbcl-1.0.19/obj/from-host/src/code/defstruct.lisp-obj-tmp"
Bye.
26.07user 1.52system 0:27.96elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+157794minor)pagefaults 0swaps
//entering make-target-1.sh
//building runtime system and symbol table file
make: Entering directory `/tmp/sbcl-1.0.19/src/runtime'
GNUmakefile:31: genesis/Makefile.features: No such file or directory
make: *** No rule to make ta</description>
    <dc:creator>Claudius Hamlet</dc:creator>
    <dc:date>2008-08-27T07:41:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11782">
    <title>FSet bug/question</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11782</link>
    <description>I'm having trouble getting FSet to run on SBCL.
http://common-lisp.net/project/fset/


* (require :fset)
...
WARNING:
    COMPILE-FILE warned while performing #&lt;COMPILE-OP NIL {100254D381}&gt; on
    #&lt;CL-SOURCE-FILE "fset" {100308BCD1}&gt;.

debugger invoked on a ASDF:COMPILE-FAILED in thread #&lt;THREAD "initial 
thread" RUNNING {100240ABE1}&gt;:
   erred while invoking #&lt;COMPILE-OP NIL {100254D381}&gt; on
   #&lt;CL-SOURCE-FILE "fset" {100308BCD1}&gt;
...


This originates in the following code snippet:
&lt;&lt;&lt;&lt;&lt;
(defvar Tuple-Keys (vector K0 K1 K2 K3 K4 K5 K6 K7 K8 K9))

(defun Test-Tuple-Operations (i)
   (let ((tup (tuple))
 (m (map))
         (typ (type-of Tuple-Keys))
 (nkeys (length Tuple-Keys))) ;; &lt;- HERE
     (print typ)
     (dotimes (j 100)
       (let ((key (svref Tuple-Keys (random nkeys)))
     (val (Make-My-Integer (random 8))))
 (setq tup (with tup key val))
 (setq m (with m key val))
 (unless (equal? m (convert 'map tup))
   (error "Tuple `with' failed on iteration ~D" i))
 (do-map (k v m)
   (unless (eq</description>
    <dc:creator>Daniel Herring</dc:creator>
    <dc:date>2008-08-26T06:51:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11781">
    <title>Test on Win32 trying to access symbols n/a in sb-posix</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11781</link>
    <description>Here's the relevent output:
 
// Running C:\cygwin\usr\local\src\sbcl-dev\sbcl-build\tests
\run-program.impure.lisp
; loading system definition from
; C:\cygwin\usr\local\src\sbcl-dev\sbcl-build\contrib\sb-grovel
\sb-grovel.asd
; into #&lt;PACKAGE "ASDF1"&gt;
; registering #&lt;SYSTEM SB-GROVEL {2430CAF9}&gt; as SB-GROVEL

debugger invoked on a SB-C::INPUT-ERROR-IN-COMPILE-FILE:
  READ failure in COMPILE-FILE:
    SB-INT:SIMPLE-READER-PACKAGE-ERROR at 1418 (line 40, column
 46) on
#&lt;SB-SYS:FD-STREAM for "file
C:\\cygwin\\usr\\local\\src\\sbcl-dev\\sbcl-build\\tests
\\run-program.impure.lisp"
{23D5CB29}&gt;:
      Symbol "PIPE" not found in the SB-POSIX package.

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [SKIP-FILE] RUN-TESTS::SKIP-FILE
  1: [CONTINUE ] Ignore and continue with next --eval option.
  2: [ABORT    ] Skip rest of --eval options.
  3:             Skip to toplevel READ/EVAL/PRINT loop.
  4: [QUIT     ] Quit SBCL (calling</description>
    <dc:creator>Matthew D. Swank</dc:creator>
    <dc:date>2008-08-25T16:39:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11779">
    <title>Possible bug in stucture printing</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11779</link>
    <description>I think I found a bug in how sbcl prints structures:

This is SBCL 1.0.19, an implementation of ANSI Common Lisp.
More information about SBCL is available at &lt;http://www.sbcl.org/&gt;.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
* (defstruct (test (:constructor make-test (&amp;key a))) (a 1) (b 2))

TEST
* (let ((*print-readably* t)) (prin1 (make-test :a 5)))
#S(TEST :A 5 :B 2)
#S(TEST :A 5 :B 2)
*


I believe in this situation sbcl should signal an error instead of 
printing.

--js


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner</description>
    <dc:creator>jacek szymanski</dc:creator>
    <dc:date>2008-08-23T22:55:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11778">
    <title>freeze for 1.0.20</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11778</link>
    <description>
I'll be releasing 1.0.20 sometime next week. Until then: testing good,
breaking things bad.

</description>
    <dc:creator>Juho Snellman</dc:creator>
    <dc:date>2008-08-23T19:19:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11773">
    <title>[PATCH] print exact times safely in TIME</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11773</link>
    <description>bug report/test case from #lisp:

&lt;wgl&gt; Holy. Cow. The 'time' function in SBCL just ate 3.1 gigs of
           my disk.  It goes wild with "Evaluation took: 15.00000*" where the
           string of zeroes stopped only when i killed the program.

 &lt;Krystof&gt; (%format-decimal *standard-output* 15000000 3) ; explodes
           for me

patch against 1.0.19 to not use %fraction when fraction is 0 in %format-decimal:

--- sbcl-1.0.19-orig/src/code/time.lisp Sat May 17 06:02:29 2008
+++ sbcl-1.0.19/src/code/time.lisp      Wed Aug 20 12:11:12 2008
&lt; at &gt;&lt; at &gt; -324,18 +324,20 &lt; at &gt;&lt; at &gt;
     (write-char #\- stream)
     (setf number (- number)))
   (let ((scale (expt 10 power)))
-    (flet ((%fraction (fraction)
-             (let ((scaled (* 10 fraction)))
-               (loop while (&lt; scaled scale)
-                     do (write-char #\0 stream)
-                        (setf scaled (* scaled 10))))
-             (format stream "~D" fraction))
-           (%zeroes ()
+    (labels ((%zeroes ()
              (let ((scaled (/ scale</description>
    <dc:creator>Bart Botta</dc:creator>
    <dc:date>2008-08-20T17:25:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11770">
    <title>Sockets as FILE-STREAMs</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11770</link>
    <description>
Hi all,

Slime's inspector tries to use PATHNAME on any kind of FILE-STREAM
object which a socket is, too. However, PATHNAME signals an (obscure)
error when being tried on a socket.

Is is sensible for sockets to be a subclass of FILE-STREAM?

  -T.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Tobias C. Rittweiler</dc:creator>
    <dc:date>2008-08-17T21:23:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11769">
    <title>problems with elephant and sbcl.</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11769</link>
    <description>-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/_______________________________________________
Sbcl-devel mailing list
Sbcl-devel&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sbcl-devel
</description>
    <dc:creator>Knut Olav Bøhmer</dc:creator>
    <dc:date>2008-08-17T13:08:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11757">
    <title>failed AVER: (TYPEP DELTA170 'UNSIGNED-BYTE)</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11757</link>
    <description>Hi,

While working on a threaded program, I realized that when I turn
profiling on and adjust worker thread count bigger than one, below
exception gets raised.

Here is the related snippet of the code:

  (defun pull-and-maximize-number-group-branches (submit-result-fn)
    (funcall
     submit-result-fn
     (maximize-product-of-generator
      (iter (for branch in
                 (mapcar #'generate-prime-branches
                         (pull-valid-number-group-batch)))
            (finding branch maximizing (length branch)))
      &gt; length)))
  
  (defun maximize-prime-sums (n-workers n-primes start end batch-size)
    (ensure-prime-number-list-big-enough (expt 2 (integer-length end)))
    (init-valid-number-group-batch n-primes start end batch-size)
    (let ((max-val)
          (max-key 0)
          (edit-lock (make-lock)))
      (flet ((submit (candidate-val)
              (with-lock-held (edit-lock)
                (let ((candidate-key (length candidate-val)))
                  (when (&lt; max-key cand</description>
    <dc:creator>Volkan YAZICI</dc:creator>
    <dc:date>2008-08-15T18:22:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11756">
    <title>Windows build failure</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11756</link>
    <description>I tried to build lates sbcl from git using mingw / gcc-4.3.1 on
Windows XP using 1.0.16.37 as bootstrap
The compile fails during creating cold core with the following error:

T
*
beginning GENESIS, creating core "output/cold-sbcl.core"
WARNING: redefining ".bss" from #X41A440 to #X417000
WARNING: redefining ".bss" from #X417000 to #X41A440
...
WARNING: redefining ".data" from #X412370 to #X4123D0
WARNING: redefining ".data" from #X4123D0 to #X412370
...
WARNING: redefining ".debug_abbrev" from #X444409 to #X443848
WARNING: redefining ".debug_abbrev" from #X443848 to #X446160
...
WARNING: redefining ".debug_aranges" from #X41D3C0 to #X41D220
WARNING: redefining ".debug_aranges" from #X41D220 to #X41D340
...
unhandled SIMPLE-ERROR: The foreign symbol "asin" is undefined.

0: (SB-DEBUG::MAP-BACKTRACE #&lt;CLOSURE (LAMBDA #) {AD00A0D}&gt;)[:EXTERNAL]
1: (SB-DEBUG:BACKTRACE 128 #&lt;SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {90957C9}&gt;)
2: (SB-DEBUG::DEBUGGER-DISABLED-HOOK
    #&lt;SIMPLE-ERROR {ACFFA21}&gt;
    #&lt;unavailable argum</description>
    <dc:creator>Marko Kocić</dc:creator>
    <dc:date>2008-08-15T13:05:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11754">
    <title>Simplifying the EBX patch (and x86 backend in general)</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11754</link>
    <description>Here's the idea:

(defmacro inst (&amp;whole whole instruction &amp;rest args &amp;environment env)
  #!+sb-doc
  "Emit the specified instruction to the current segment. INSTRUCTION
can either be a symbol naming the instruction, or a list of two element,
first naming a prefix, the second naming the instruction."
  (if (consp instruction)
      (destructuring-bind (prefix name) instruction
        (aver (and (symbolp prefix) (symbolp name)))
        `(progn
           (inst ,(symbolicate prefix "-PREFIX"))
           (inst ,name ,&lt; at &gt;args)))
      (let ((inst (gethash (symbol-name instruction) *assem-instructions*)))
        (cond ((null inst)
               (error "unknown instruction: ~S" instruction))
              ((functionp inst)
               (funcall inst (cdr whole) env))
              (t
               `(,inst (%%current-segment%%) (%%current-vop%%) ,&lt; at &gt;args))))))

and renaming FS-SEGMENT-PREFIX to FS-PREFIX.

So that you can use

 (inst (fs &lt;instruction&gt;) ...args...)

instead of

 (inst fs-segment-prefix)
 (inst &lt;</description>
    <dc:creator>Nikodemus Siivola</dc:creator>
    <dc:date>2008-08-15T09:55:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11749">
    <title>SBCL website not updated...</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11749</link>
    <description>Hi,

Just a note: The SBCL website still says that the version is at  
1.0.18. This almost made me miss 1.0.19...

Best,
Pascal

</description>
    <dc:creator>Pascal Costanza</dc:creator>
    <dc:date>2008-08-14T12:11:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11747">
    <title>[PATCH] Use list designator for SHADOWING-IMPORT(overlooked in 1.0.19.15)</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11747</link>
    <description>
Signed-off-by: Michael Weber &lt;michaelw+sbcl&lt; at &gt;foldr.org&gt;
---
 src/code/target-package.lisp |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/src/code/target-package.lisp b/src/code/target-package.lisp
index e92c43f..9c10525 100644
--- a/src/code/target-package.lisp
+++ b/src/code/target-package.lisp
&lt; at &gt;&lt; at &gt; -883,7 +883,7 &lt; at &gt;&lt; at &gt; implementation it is ~S." *default-package-use-list*)
                  (if (eq package-symbol chosen-symbol)
                      nil                ; re-importing the same symbol
                      (shadowing-import (list chosen-symbol) package))
-                 (shadowing-import chosen-symbol package)))))))))
+                 (shadowing-import (list chosen-symbol) package)))))))))
 
 ;;; If we are uninterning a shadowing symbol, then a name conflict can
 ;;; result, otherwise just nuke the symbol.
</description>
    <dc:creator>Michael Weber</dc:creator>
    <dc:date>2008-08-12T22:25:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11739">
    <title>REPLACE transforms</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11739</link>
    <description>In a function with (speed 3) I had (replace s1 s2 :start1 start) and 
lived peacefully in the belief that all is well and fast until sbcl ran 
out of memory in replace.

I found that :START1 inhibited the double-float double-float 
deftransform for replace and it ended up consing up a double and 
sticking it into the target array for each element which needles to say 
is both slow and wasteful.

The attached patch makes the deftransform deal with this more 
gracefully: instead of punting if START1 and START2 aren't the same 
constant it leaves the decision until run time about whether it's a 
forward or backward copy.

It does not register in sbcl self compile neither in cl-bench 
performance. But coupled with gc conservatism this is the difference 
for my app between running out of heap or chugging along.

Cheers, Gabor
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applicati</description>
    <dc:creator>Gábor Melis</dc:creator>
    <dc:date>2008-08-07T16:25:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11734">
    <title>[PATCH] Added more files to .gitignore</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11734</link>
    <description>
Signed-off-by: Michael Weber &lt;michaelw+sbcl&lt; at &gt;foldr.org&gt;
---
 .gitignore            |    1 +
 doc/manual/.gitignore |   27 +++++++++++++++++++++++++++
 tests/.gitignore      |    1 +
 3 files changed, 29 insertions(+), 0 deletions(-)
 create mode 100644 doc/manual/.gitignore
 create mode 100644 tests/.gitignore

diff --git a/.gitignore b/.gitignore
index 33f182d..6ef4ad7 100644
--- a/.gitignore
+++ b/.gitignore
&lt; at &gt;&lt; at &gt; -1,4 +1,5 &lt; at &gt;&lt; at &gt;
 *.d
+*.dSYM
 *.o
 *.fasl
 *.FASL
diff --git a/doc/manual/.gitignore b/doc/manual/.gitignore
new file mode 100644
index 0000000..2320edf
--- /dev/null
+++ b/doc/manual/.gitignore
&lt; at &gt;&lt; at &gt; -0,0 +1,27 &lt; at &gt;&lt; at &gt;
+*.aux
+*.cp
+*.cps
+*.fn
+*.fns
+*.ky
+*.log
+*.pg
+*.texi-temp
+*.toc
+*.tp
+*.tps
+*.vr
+*.vrs
+asdf.info*
+asdf.pdf
+asdf.ps
+asdf.texinfo
+asdf/
+docstrings/
+html-stamp
+sbcl.info*
+sbcl.pdf
+sbcl.ps
+sbcl/
+tempfiles-stamp
+variables.texinfo
diff --git a/tests/.gitignore b/tests/.gitignore
new file mode 100644
index 0000000..2a92d27
--- /dev/null
+++ b/tests/.gitignore
&lt; at &gt;&lt; at &gt; -0,0 +1 &lt; at &gt;&lt; at &gt;
+ext</description>
    <dc:creator>Michael Weber</dc:creator>
    <dc:date>2008-08-06T08:57:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11733">
    <title>[PATCH] Fixed formatting of FORMAT docstring</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11733</link>
    <description>
Signed-off-by: Michael Weber &lt;michaelw+sbcl&lt; at &gt;foldr.org&gt;
---
 src/code/target-format.lisp |   36 ++++++++++++++++++------------------
 1 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/src/code/target-format.lisp b/src/code/target-format.lisp
index 890b943..18b1cee 100644
--- a/src/code/target-format.lisp
+++ b/src/code/target-format.lisp
&lt; at &gt;&lt; at &gt; -16,27 +16,27 &lt; at &gt;&lt; at &gt;
 (defun format (destination control-string &amp;rest format-arguments)
   #!+sb-doc
   "Provides various facilities for formatting output.
-  CONTROL-STRING contains a string to be output, possibly with embedded
-  directives, which are flagged with the escape character \"~\". Directives
-  generally expand into additional text to be output, usually consuming one
-  or more of the FORMAT-ARGUMENTS in the process. A few useful directives
-  are:
-        ~A or ~nA   Prints one argument as if by PRINC
-        ~S or ~nS   Prints one argument as if by PRIN1
-        ~D or ~nD   Prints one argument as a decimal integer
-        ~%          Does a T</description>
    <dc:creator>Michael Weber</dc:creator>
    <dc:date>2008-08-06T08:37:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11723">
    <title>[PATCH] SBCL Manual fixes</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11723</link>
    <description>Hi,
just a few patches for some issues I found going through the manual.


Xan
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/_______________________________________________
Sbcl-devel mailing list
Sbcl-devel&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sbcl-devel
</description>
    <dc:creator>Xan</dc:creator>
    <dc:date>2008-08-04T10:26:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11721">
    <title>UNWIND-PROTECT interferes with type inference in mvcombinations</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11721</link>
    <description>Just noticed this:

First:

(in-package :sb-c)

(defknown compiler-derived-type (t) (values t t) (movable flushable unsafe))

(deftransform compiler-derived-type ((x))
 `(values ',(type-specifier (lvar-type x)) t))

Now, as expected:

CL-USER&gt; (funcall
          (lambda (x y)
            (multiple-value-bind (s w)
                (find-symbol x y)
              (values (sb-c::compiler-derived-type s)
(sb-c::compiler-derived-type w))))
          "FOO" :cl-user)
SYMBOL
(MEMBER :INTERNAL :EXTERNAL :INHERITED NIL)

and:

CL-USER&gt; (funcall
          (lambda (x y)
            (declare (optimize (sb-c::let-conversion 0)))
            (unwind-protect
                 (let ((s (find-symbol x y)))
                   (sb-c::compiler-derived-type s))
              t))
          "FOO" :cl-user)
SYMBOL
T

No problems with an MV combination, or a a regular one inside an UNWIND-PROTECT.

However:

CL-USER&gt; (funcall
          (lambda (x y)
            (unwind-protect
                 (multiple-value-bind (s w)
              </description>
    <dc:creator>Nikodemus Siivola</dc:creator>
    <dc:date>2008-08-03T22:51:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11718">
    <title>GC questions</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11718</link>
    <description>-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/_______________________________________________
Sbcl-devel mailing list
Sbcl-devel&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sbcl-devel
</description>
    <dc:creator>Cedric St-Jean</dc:creator>
    <dc:date>2008-08-02T18:13:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11712">
    <title>Incrementally mutating the type of a generic function</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11712</link>
    <description>Hello,

When a generic function has &amp;KEY but not &amp;ALLOW-OTHER-KEYS in the lambda
list, the compiler will issue STYLE-WARNINGs in cases where it might be
reasonable not to.  Example:

* (defgeneric foo (x &amp;key))
#&lt;STANDARD-GENERIC-FUNCTION FOO (0)&gt;
* (defmethod foo (x &amp;key bar)
    (list x bar))
#&lt;STANDARD-METHOD FOO (T) {5147B6C1}&gt;
* (defun baz () (foo 1 :bar 10))
; in: LAMBDA NIL
;     (FOO 1 :BAR 10)
; 
; caught STYLE-WARNING:
;   :BAR is not a known argument keyword.
; 
; compilation unit finished
;   caught 1 STYLE-WARNING condition
BAZ

While it's desirable for the compiler to detect mistakes (and so it's
not good, IMO, to have generic functions's types implicitly include
&amp;ALLOW-OTHER-KEYS if the gf takes any keywords), I think it would be
nice to have method addition and removal incrementally change the
compiler's idea of what keys the gf will accept, and to use the union of
them in the compiler's idea of the type of the function.  (The union is
too big in general, but ISTM there's little payoff to try</description>
    <dc:creator>Richard M Kreuter</dc:creator>
    <dc:date>2008-08-01T18:04:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.steel-bank.devel/11708">
    <title>[PATCH] Unbreak RESOLVE-CONFLICT restart</title>
    <link>http://comments.gmane.org/gmane.lisp.steel-bank.devel/11708</link>
    <description>* USEing packages with conflicting symbols:

    (defpackage "X" (:use) (:export "X0"))
    (defun x:x0 () 'x:x0)

    (defpackage "Y" (:use) (:export "X0"))
    (defun y:x0 () 'y:x0)

    (defpackage "XY" (:use))

    (use-package '("X" "Y") (find-package "XY"))

    ...signals SB-EXT:NAME-CONFLICT.  Choose RESOLVE-CONFLICT:
    Select a symbol to be made accessible in package XY:
      1. X:X0
      2. Y:X0

    Enter an integer (between 1 and 2): 2

    CL-USER&gt; (xy::x0) ; should be EQ Y:X0 now!

    ; in: LAMBDA NIL
    ;     (XY::X0)
    ;
    ; caught STYLE-WARNING:
    ;   undefined function: XY::X0

* Correctly handle conflicts involving CL:NIL by passing (list symbol)
  to package frobbing functions which take a list designator.

Signed-off-by: Michael Weber &lt;michaelw+sbcl&lt; at &gt;foldr.org&gt;
---
 src/code/target-package.lisp |   46 ++++++++++++++++++++++++-----------------
 1 files changed, 27 insertions(+), 19 deletions(-)

diff --git a/src/code/target-package.lisp b/src/code/target-package.lisp
index 937c</description>
    <dc:creator>Michael Weber</dc:creator>
    <dc:date>2008-08-01T13:02:23</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.lisp.steel-bank.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.lisp.steel-bank.devel</link>
  </textinput>
</rdf:RDF>
