... as documented, but not as actually done.
Reported by Maciej Katafiasz sbcl-devel 2008-01-13
Also slightly better documentation links for *posix-argv*.
;;;; -*- coding: utf-8; -*-
+changes in sbcl-1.0.14 relative to sbcl-1.0.13:
+ * bug fix: RESOLVE-CONFLICT (and the other name conflict machinery)
+ is now actually exported from SB-EXT as documented. (reported by
+ Maciej Katafiasz)
+
changes in sbcl-1.0.13 relative to sbcl-1.0.12:
* minor incompatible change: RUN-PROGRAM now uses execvp(3) to find
an executable in the search path, and does so in the child
@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
@code{sb-ext:*posix-argv*}.
@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}.
@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
@node Unix-style Command Line Protocol
@comment node-name, next, previous, up
@subsubsection Unix-style Command Line Protocol
+@vindex sb-ext:*posix-argv*
+@vindex *posix-argv*
Standard Unix tools that are interpreters follow a common command line
protocol that is necessary to work with ``shebang scripts''. SBCL
"IMPLICIT-GENERIC-FUNCTION-WARNING"
"INVALID-FASL"
+ "NAME-CONFLICT" "NAME-CONFLICT-FUNCTION"
+ "NAME-CONFLICT-DATUM" "NAME-CONFLICT-SYMBOLS"
+ "RESOLVE-CONFLICT"
+
;; and a mechanism for controlling same at compile time
"MUFFLE-CONDITIONS" "UNMUFFLE-CONDITIONS"
"FORMAT-TOO-MANY-ARGS-WARNING" "EXTENSION-FAILURE"
"STRUCTURE-INITARG-NOT-KEYWORD" "CONSTANT-MODIFIED"
- "NAME-CONFLICT" "NAME-CONFLICT-FUNCTION"
- "NAME-CONFLICT-DATUM" "NAME-CONFLICT-SYMBOLS"
- "RESOLVE-CONFLICT"
-
;; ..and DEFTYPEs..
"INDEX" "LOAD/STORE-INDEX"
"SIGNED-BYTE-WITH-A-BITE-OUT"
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.13.12"
+"1.0.13.13"