0.6.12.26:

[sbcl.git] / doc / beyond-ansi.sgml

diff --git a/doc/beyond-ansi.sgml b/doc/beyond-ansi.sgml
index 3c1a434..ff1cce5 100644 (file)
--- a/doc/beyond-ansi.sgml
+++ b/doc/beyond-ansi.sgml
@@ -49,7 +49,7 @@ and call
 
 you will not get the correct result, but an error,
 
 
 you will not get the correct result, but an error,
 

-<screen>debugger invoked on SB-DEBUG::*DEBUG-CONDITION* of type
+<screen>debugger invoked on SB-DEBUG:*DEBUG-CONDITION* of type

 SB-KERNEL:SIMPLE-CONTROL-ERROR:
   A function with declared result type NIL returned:
   FOO-P</screen>
 SB-KERNEL:SIMPLE-CONTROL-ERROR:
   A function with declared result type NIL returned:
   FOO-P</screen>

@@ -130,18 +130,13 @@ calling external C code, described
 specified by &ANSI;. Weak pointers allow references to objects to be
 maintained without keeping them from being GCed. And "finalization"
 hooks are available to cause code to be executed when an object is
 specified by &ANSI;. Weak pointers allow references to objects to be
 maintained without keeping them from being GCed. And "finalization"
 hooks are available to cause code to be executed when an object is

-GCed.</para>
+GCed.</para> <!-- FIXME: Actually documenting these would be good.:-| -->

 
 <para>&SBCL; does not currently provide Gray streams, but may do so in
 the near future. (It has unmaintained code inherited from &CMUCL; to
 do so.) <!-- FIXME: Add citation to Gray streams.-->
 </para>
 
 
 <para>&SBCL; does not currently provide Gray streams, but may do so in
 the near future. (It has unmaintained code inherited from &CMUCL; to
 do so.) <!-- FIXME: Add citation to Gray streams.-->
 </para>
 

-<para>&SBCL; does not currently support multithreading (traditionally
-called <wordasword>multiprocessing</> in &Lisp;) but contains unmaintained
-code from &CMUCL; to do so. A sufficiently motivated maintainer
-could probably make it work.</para>
-

 </sect2>
 
 <sect2><title>Support for Unix</>
 </sect2>
 
 <sect2><title>Support for Unix</>

@@ -165,6 +160,14 @@ is also supported.</para>
 
 <para>The debugger supports a number of options. Its documentation is
 accessed by typing <userinput>help</> at the debugger prompt.</para>
 
 <para>The debugger supports a number of options. Its documentation is
 accessed by typing <userinput>help</> at the debugger prompt.</para>

+<!-- FIXME:
+     A true debugger section in the manual would be good. Start
+     with CMU CL's debugger section, but remember:
+       * no QUIT command (TOPLEVEL restart instead)
+       * no GO command (CONTINUE restart instead)
+       * Limitations of the x86 port of the debugger should be 
+         documented or fixed where possible.
+       * Discuss TRACE and its unification with PROFILE. -->

 
 <para>Documentation for <function>inspect</> is accessed by typing
 <userinput>help</> at the <function>inspect</> prompt.</para>
 
 <para>Documentation for <function>inspect</> is accessed by typing
 <userinput>help</> at the <function>inspect</> prompt.</para>