1.0.27.30: minor octets.lisp cleanup

[sbcl.git] / doc / manual / beyond-ansi.texinfo

diff --git a/doc/manual/beyond-ansi.texinfo b/doc/manual/beyond-ansi.texinfo
index dedf819..a00ae6a 100644 (file)
--- a/doc/manual/beyond-ansi.texinfo
+++ b/doc/manual/beyond-ansi.texinfo
@@ -7,14 +7,15 @@ ANSI standard. SBCL doesn't support as many extensions as CMUCL, but
 it still has quite a few.  @xref{Contributed Modules}.
 
 @menu
 it still has quite a few.  @xref{Contributed Modules}.
 
 @menu

-* Garbage Collection::          
-* Metaobject Protocol::         
-* Support For Unix::            
-* Customization Hooks for Users::  
-* Tools To Help Developers::    
-* Resolution of Name Conflicts::  
-* Stale Extensions::            
-* Efficiency Hacks::            
+* Garbage Collection::
+* Metaobject Protocol::
+* Support For Unix::
+* Customization Hooks for Users::
+* Tools To Help Developers::
+* Resolution of Name Conflicts::
+* Miscellaneous Extensions::
+* Stale Extensions::
+* Efficiency Hacks::

 @end menu
 
 @node  Garbage Collection
 @end menu
 
 @node  Garbage Collection

@@ -43,7 +44,7 @@ with AMOP; present exceptions to this (as distinct from current bugs)
 are:
 
 @itemize
 are:
 
 @itemize

-  
+

 @item
 @findex compute-effective-method
 @findex sb-mop:compute-effective-method
 @item
 @findex compute-effective-method
 @findex sb-mop:compute-effective-method

@@ -67,7 +68,7 @@ the standardized classes before @code{t} appearing in the class
 precedence list of @code{generic-function} and
 @code{standard-generic-function}, as required by section 1.4.4.5 of the
 ANSI specification.
 precedence list of @code{generic-function} and
 @code{standard-generic-function}, as required by section 1.4.4.5 of the
 ANSI specification.

-  
+

 @item
 @findex ensure-generic-function
 @findex generic-function-declarations
 @item
 @findex ensure-generic-function
 @findex generic-function-declarations

@@ -257,9 +258,11 @@ between classes and proper names and between lists of the form
 
 @node Command-line arguments
 @subsection Command-line arguments
 
 @node Command-line arguments
 @subsection Command-line arguments

+@vindex sb-ext:*posix-argv*
+@vindex *posix-argv*

 
 The UNIX command line can be read from the variable
 
 The UNIX command line can be read from the variable

-@code{sb-ext:*posix-argv*}. 
+@code{sb-ext:*posix-argv*}.

 
 @node Querying the process environment
 @subsection Querying the process environment
 
 @node Querying the process environment
 @subsection Querying the process environment

@@ -335,9 +338,19 @@ mechanisms as follows:
 @include fun-common-lisp-ed.texinfo
 @include var-sb-ext-star-ed-functions-star.texinfo
 
 @include fun-common-lisp-ed.texinfo
 @include var-sb-ext-star-ed-functions-star.texinfo
 

+Conditions of type @code{warning} and @code{style-warning} are
+sometimes signaled at runtime, especially during execution of Common
+Lisp defining forms such as @code{defun}, @code{defmethod}, etc.  To
+muffle these warnings at runtime, SBCL provides a variable
+@code{sb-ext:*muffled-warnings*}:
+
+@include var-sb-ext-star-muffled-warnings-star.texinfo
+

 @node Tools To Help Developers
 @comment  node-name,  next,  previous,  up
 @section Tools To Help Developers
 @node Tools To Help Developers
 @comment  node-name,  next,  previous,  up
 @section Tools To Help Developers

+@findex trace
+@findex inspect

 
 SBCL provides a profiler and other extensions to the ANSI @code{trace}
 facility.  For more information, see @ref{Macro common-lisp:trace}.
 
 SBCL provides a profiler and other extensions to the ANSI @code{trace}
 facility.  For more information, see @ref{Macro common-lisp:trace}.

@@ -350,6 +363,10 @@ the @code{inspect} prompt.
 
 @node Resolution of Name Conflicts
 @section Resolution of Name Conflicts
 
 @node Resolution of Name Conflicts
 @section Resolution of Name Conflicts

+@tindex sb-ext:name-conflict
+@tindex name-conflict
+@findex sb-ext:name-conflict-symbols
+@findex name-conflict-symbols

 
 The ANSI standard (section 11.1.1.2.5) requires that name conflicts in
 packages be resolvable in favour of any of the conflicting symbols.  In
 
 The ANSI standard (section 11.1.1.2.5) requires that name conflicts in
 packages be resolvable in favour of any of the conflicting symbols.  In

@@ -359,6 +376,12 @@ the @code{sb-ext:resolve-conflict} restart should be invoked with one
 argument, which should be a member of the list returned by the condition
 accessor @code{sb-ext:name-conflict-symbols}.
 
 argument, which should be a member of the list returned by the condition
 accessor @code{sb-ext:name-conflict-symbols}.
 

+@node    Miscellaneous Extensions
+@comment  node-name,  next,  previous,  up
+@section Miscellaneous Extensions
+
+@include fun-sb-ext-array-storage-vector.texinfo
+

 @node Stale Extensions
 @comment  node-name,  next,  previous,  up
 @section Stale Extensions
 @node Stale Extensions
 @comment  node-name,  next,  previous,  up
 @section Stale Extensions

@@ -415,5 +438,5 @@ to it. This is appropriate for functions like @code{sqrt}, but
 is @emph{not} appropriate for functions like @code{aref},
 which can change their return values when the underlying data are
 changed.
 is @emph{not} appropriate for functions like @code{aref},
 which can change their return values when the underlying data are
 changed.

-@c <!-- FIXME: This declaration does not seem to be supported in the 
+@c <!-- FIXME: This declaration does not seem to be supported in the

 @c      current compiler. -->
 @c      current compiler. -->