0.8.1.50
[sbcl.git] / package-data-list.lisp-expr
index 63ba1ba..b117d4b 100644 (file)
@@ -213,6 +213,8 @@ of SBCL which maintained the CMU-CL-style split into two packages.)"
               "COMPILE-IN-LEXENV"
              "COMPILE-LAMBDA-FOR-DEFUN"
               "%COMPILER-DEFUN" "COMPILER-ERROR"
+             "COMPILER-NOTIFY"
+             "COMPILER-STYLE-WARN" "COMPILER-WARN"
               "COMPONENT" "COMPONENT-HEADER-LENGTH"
               "COMPONENT-INFO" "COMPONENT-LIVE-TN" "COMPUTE-FUN"
               "COMPUTE-OLD-NFP" "COPY-MORE-ARG"
@@ -248,7 +250,7 @@ of SBCL which maintained the CMU-CL-style split into two packages.)"
               "MAKE-OTHER-IMMEDIATE-TYPE" "MAKE-RANDOM-TN"
               "MAKE-REPRESENTATION-TN" "MAKE-RESTRICTED-TN" "MAKE-SC-OFFSET"
               "MAKE-STACK-POINTER-TN" "MAKE-TN-REF" "MAKE-UNWIND-BLOCK"
-             "MAKE-WIRED-TN" "MAYBE-COMPILER-NOTE"
+             "MAKE-WIRED-TN" "MAYBE-COMPILER-NOTIFY"
              "MAYBE-INLINE-SYNTACTIC-CLOSURE"
               "META-PRIMITIVE-TYPE-OR-LOSE"
               "META-SB-OR-LOSE" "META-SC-NUMBER-OR-LOSE" "META-SC-OR-LOSE"
@@ -499,12 +501,9 @@ like *STACK-TOP-HINT* and unsupported stuff like *TRACED-FUN-LIST*."
  ;; symbols in package COMMON-LISP. Lots of these symbols are accessed
  ;; with explicit SB!IMPL:: prefixes in the code. It would be nice to
  ;; reduce the use of this practice, so if symbols from here which are
- ;; accessed that way are found to belong more appropriately in
- ;; an existing package (e.g. KERNEL or SYS or EXT or FASL), I
- ;; (WHN 19990223) encourage maintainers to move them there..
- ;;
- ;; ..except that it's getting so big and crowded that maybe it should
- ;; be split up, too.
+ ;; accessed that way are found to belong more appropriately in an
+ ;; existing package (e.g. SB!KERNEL or SB!SYS or SB!EXT or SB!FASL),
+ ;; I (WHN 19990223) encourage maintainers to move them there..
  #s(sb-cold:package-data
     :name "SB!IMPL"
     :doc "private: a grab bag of implementation details"
@@ -546,6 +545,15 @@ like *STACK-TOP-HINT* and unsupported stuff like *TRACED-FUN-LIST*."
              ;; error reporting, we have
              "DEFINE-SOURCE-CONTEXT"
 
+            ;; and given how many users dislike strict treatment of
+            ;; DEFCONSTANT, let's give them enough rope to escape by
+            "DEFCONSTANT-UNEQL" "DEFCONSTANT-UNEQL-NAME"
+            "DEFCONSTANT-UNEQL-NEW-VALUE" "DEFCONSTANT-UNEQL-OLD-VALUE"
+
+            ;; conditions that can be handled to reduce compiler
+            ;; verbosity
+            "COMPILER-NOTE"
+
             ;; FIXME: This name doesn't match the DEFFOO - vs. -
             ;; DEFINE-FOO convention used in the ANSI spec, and so
             ;; was deprecated in sbcl-0.pre7, ca. 2001-12-12. After
@@ -628,6 +636,7 @@ like *STACK-TOP-HINT* and unsupported stuff like *TRACED-FUN-LIST*."
              ;; return a PROCESS object with operations defined on
              ;; that object.
              "RUN-PROGRAM"
+            "FIND-EXECUTABLE-IN-SEARCH-PATH"
              "PROCESS-ALIVE-P" "PROCESS-CLOSE"
              "PROCESS-CORE-DUMPED" "PROCESS-ERROR" "PROCESS-EXIT-CODE"
              "PROCESS-INPUT" "PROCESS-KILL" "PROCESS-OUTPUT" "PROCESS-P"
@@ -701,8 +710,8 @@ retained, possibly temporariliy, because it might be used internally."
              "SIMPLE-PROGRAM-ERROR" "SIMPLE-STREAM-ERROR"
              "SIMPLE-STYLE-WARNING"
             "SPECIAL-FORM-FUNCTION"
-             "STYLE-WARN"
-
+             "STYLE-WARN" "SIMPLE-COMPILER-NOTE"
+            
              ;; bootstrapping magic, to make things happen both in
              ;; the cross-compilation host compiler's environment and
              ;; in the cross-compiler's environment
@@ -874,6 +883,8 @@ retained, possibly temporariliy, because it might be used internally."
              "POSITIVE-PRIMEP"
              "EVAL-IN-LEXENV"
             "DEBUG-NAMIFY"
+             "FORCE" "DELAY" "PROMISE-READY-P"
+            "FIND-RESTART-OR-CONTROL-ERROR"
 
              ;; These could be moved back into SB!EXT if someone has
              ;; compelling reasons, but hopefully we can get by
@@ -1016,7 +1027,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "ARRAY-TYPE-DIMENSIONS" "ARRAY-TYPE-ELEMENT-TYPE"
              "ARRAY-TYPE-P"
              "ARRAY-TYPE-SPECIALIZED-ELEMENT-TYPE" "ASH-INDEX"
-             "ASSERT-ERROR" "BASE-CHAR-P"
+             "ASSERT-ERROR" "BASE-CHAR-P" "BASE-STRING-P"
              "BINDING-STACK-POINTER-SAP" "BIT-BASH-COPY"
              "BIT-INDEX" "BOGUS-ARG-TO-VALUES-LIST-ERROR"
              "BOOLE-CODE"
@@ -1070,18 +1081,22 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "FIND-AND-INIT-OR-CHECK-LAYOUT"
              "FLOAT-EXPONENT" "FLOAT-FORMAT-DIGITS" "FLOAT-FORMAT-NAME"
              "FLOAT-FORMAT-MAX" "FLOATING-POINT-EXCEPTION"
-             "FORM" "*FREE-INTERRUPT-CONTEXT-INDEX*" "FUNCALLABLE-INSTANCE-P"
-             "FUN-CODE-HEADER" 
+             "FORM"
+             "FORMAT-CONTROL"
+             "*FREE-INTERRUPT-CONTEXT-INDEX*" "FUNCALLABLE-INSTANCE-P"
+             "FUN-CODE-HEADER"
              "FUN-TYPE" "FUN-TYPE-ALLOWP"
              "FUN-TYPE-KEYP" "FUN-TYPE-KEYWORDS"
              "FUN-TYPE-NARGS" "FUN-TYPE-OPTIONAL"
              "FUN-TYPE-P"
              "FUN-TYPE-REQUIRED" "FUN-TYPE-REST"
              "FUN-TYPE-RETURNS" "FUN-TYPE-WILD-ARGS"
-             "FUN-WORD-OFFSET" "GET-CLOSURE-LENGTH"
+             "FUN-WORD-OFFSET"
+             "GENERALIZED-BOOLEAN"
+             "GET-CLOSURE-LENGTH"
              "GET-HEADER-DATA"
-             "GET-LISP-OBJ-ADDRESS" "LOWTAG-OF"
-             "WIDETAG-OF"
+             "GET-LISP-OBJ-ADDRESS" "LOWTAG-OF" "WIDETAG-OF"
+            "GET-MACHINE-VERSION"
              "HAIRY-DATA-VECTOR-REF" "HAIRY-DATA-VECTOR-SET" "HAIRY-TYPE"
              "HAIRY-TYPE-CHECK-TEMPLATE-NAME" "HAIRY-TYPE-SPECIFIER"
              "HANDLE-CIRCULARITY" "HOST" "IGNORE-IT"
@@ -1155,6 +1170,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "NUMERIC-TYPE-FORMAT"
              "NUMERIC-TYPE-HIGH" "NUMERIC-TYPE-LOW" "NUMERIC-TYPE-P"
              "OBJECT-NOT-ARRAY-ERROR" "OBJECT-NOT-BASE-CHAR-ERROR"
+            "OBJECT-NOT-BASE-STRING-ERROR"
              "OBJECT-NOT-BIGNUM-ERROR" "OBJECT-NOT-BIT-VECTOR-ERROR"
              "OBJECT-NOT-COMPLEX-ERROR"
              "OBJECT-NOT-COMPLEX-FLOAT-ERROR"
@@ -1196,6 +1212,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "OBJECT-NOT-SIMPLE-ARRAY-SIGNED-BYTE-32-ERROR"
              "OBJECT-NOT-SIMPLE-ARRAY-SIGNED-BYTE-8-ERROR"
              "OBJECT-NOT-SIMPLE-BIT-VECTOR-ERROR"
+            "OBJECT-NOT-SIMPLE-BASE-STRING-ERROR"
              "OBJECT-NOT-SIMPLE-STRING-ERROR"
              "OBJECT-NOT-SIMPLE-VECTOR-ERROR"
              "OBJECT-NOT-SINGLE-FLOAT-ERROR" "OBJECT-NOT-STRING-ERROR"
@@ -1214,6 +1231,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              #!+x86 "*PSEUDO-ATOMIC-INTERRUPTED*"
              "PUNT-PRINT-IF-TOO-LONG"
              "READER-IMPOSSIBLE-NUMBER-ERROR" "READER-PACKAGE-ERROR"
+             "RESTART-DESIGNATOR"
              "SCALE-DOUBLE-FLOAT"
             #!+long-float "SCALE-LONG-FLOAT"
              "SCALE-SINGLE-FLOAT"
@@ -1238,6 +1256,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "SIMPLE-ARRAY-SIGNED-BYTE-30-P"
              "SIMPLE-ARRAY-SIGNED-BYTE-32-P"
              "SIMPLE-ARRAY-SIGNED-BYTE-8-P"
+            "SIMPLE-BASE-STRING-P"
              "SIMPLE-PACKAGE-ERROR"
              "SIMPLE-UNBOXED-ARRAY"
              "SINGLE-FLOAT-BITS" "SINGLE-FLOAT-EXPONENT"
@@ -1252,7 +1271,8 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "%INSTANCE-LENGTH"
              "%INSTANCE-REF" "%INSTANCE-SET"
              "SYSTEM-AREA-CLEAR"
-             "SYSTEM-AREA-COPY" "TWO-ARG-*"
+             "SYSTEM-AREA-COPY"
+             "TWO-ARG-*"
              "TWO-ARG-+" "TWO-ARG--"
              "TWO-ARG-/" "TWO-ARG-/=" "TWO-ARG-<"
              "TWO-ARG-<=" "TWO-ARG-="
@@ -1277,13 +1297,15 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "VALUES-SPECIFIER-TYPE-CACHE-CLEAR" "VALUES-SUBTYPEP"
              "VALUES-TYPE"
              "VALUES-TYPE-ERROR"
+             "VALUES-TYPE-IN"
              "VALUES-TYPE-INTERSECTION"
              "VALUES-TYPE-OPTIONAL"
+             "VALUES-TYPE-OUT"
              "VALUES-TYPE-P" "VALUES-TYPE-REQUIRED"
              "VALUES-TYPE-REST" "VALUES-TYPE-UNION"
              "VALUES-TYPE-TYPES" "VALUES-TYPES"
-             "VALUES-TYPE-START"
              "VALUES-TYPES-EQUAL-OR-INTERSECT" "VECTOR-T-P"
+            "VECTOR-NIL-P"
              "VECTOR-TO-VECTOR*"
              "VECTOR-OF-CHECKED-LENGTH-GIVEN-LENGTH"
              "WITH-ARRAY-DATA"
@@ -1309,7 +1331,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "*TYPE-SYSTEM-INITIALIZED*" "FIND-LAYOUT"
              "DSD-NAME" "%TYPEP" "DD-RAW-INDEX"
              "DD-NAME" "CLASSOID-SUBCLASSES"
-             "CLASSOID-LAYOUT" "CLASSOID-NAME"
+             "CLASSOID-LAYOUT" "CLASSOID-NAME" "CLASSOID-P"
              "DD-RAW-LENGTH" "NOTE-NAME-DEFINED"
              "%CODE-CODE-SIZE" "DD-SLOTS"
             "DD-INCLUDE" "SLOT-SETTER-LAMBDA-FORM"
@@ -1369,9 +1391,10 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
 
              ;; symbols from former SB!CONDITIONS
              "*HANDLER-CLUSTERS*" "*RESTART-CLUSTERS*"
+            "*CONDITION-RESTARTS*"
              "SHOW-CONDITION" "CASE-FAILURE"
              "NAMESTRING-PARSE-ERROR" "NAMESTRING-PARSE-ERROR-OFFSET"
-             "DESCRIBE-CONDITION"
+             "DESCRIBE-CONDITION" "MAKE-RESTART" "COERCE-TO-CONDITION"
 
             "CONDITION-READER-FUNCTION" "CONDITION-WRITER-FUNCTION"
             
@@ -1386,6 +1409,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "!TYPE-CLASS-COLD-INIT" "!TYPEDEFS-COLD-INIT"
              "!ALIEN-TYPE-COLD-INIT" "!CLASSES-COLD-INIT"
              "!EARLY-TYPE-COLD-INIT" "!LATE-TYPE-COLD-INIT"
+            "!FIXUP-TYPE-COLD-INIT"
              "!TARGET-TYPE-COLD-INIT" "!RANDOM-COLD-INIT"
              "!READER-COLD-INIT" "!TYPECHECKFUNS-COLD-INIT"
              "STREAM-COLD-INIT-OR-RESET" "!LOADER-COLD-INIT"
@@ -1393,6 +1417,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "!PACKAGE-COLD-INIT" "SIGNAL-COLD-INIT-OR-REINIT"
              "!POLICY-COLD-INIT-OR-RESANIFY" "!VM-TYPE-COLD-INIT"
              "!BACKQ-COLD-INIT" "!SHARPM-COLD-INIT"
+            "!EARLY-PROCLAIM-COLD-INIT" "!LATE-PROCLAIM-COLD-INIT"
              "!CLASS-FINALIZE" "GC-REINIT"
 
              ;; Note: These are out of lexicographical order because in CMU CL
@@ -1898,7 +1923,8 @@ structure representations"
              "COMPLEX-SINGLE-FLOAT-IMAG-SLOT" "COMPLEX-SINGLE-FLOAT-REAL-SLOT"
              "COMPLEX-SINGLE-FLOAT-SIZE" "COMPLEX-SINGLE-FLOAT-WIDETAG"
              "COMPLEX-SINGLE-REG-SC-NUMBER" "COMPLEX-SINGLE-STACK-SC-NUMBER"
-             "COMPLEX-SIZE" "COMPLEX-STRING-WIDETAG" "COMPLEX-WIDETAG"
+             "COMPLEX-SIZE" "COMPLEX-BASE-STRING-WIDETAG" "COMPLEX-WIDETAG"
+            "COMPLEX-VECTOR-NIL-WIDETAG"
              "COMPLEX-VECTOR-WIDETAG" "CONS-CAR-SLOT" "CONS-CDR-SLOT"
              "CONS-SIZE" "CONSTANT-SC-NUMBER"
              "CONTEXT-FLOATING-POINT-MODES" "CONTEXT-FLOAT-REGISTER"
@@ -1988,6 +2014,11 @@ structure representations"
              "*READ-ONLY-SPACE-FREE-POINTER*"
              "REGISTER-SAVE-PENALTY" "RETURN-PC-HEADER-WIDETAG"
              "RETURN-PC-RETURN-POINT-OFFSET" "RETURN-PC-SAVE-OFFSET"
+            "SAETP-CTYPE" "SAETP-INITIAL-ELEMENT-DEFAULT"
+            "SAETP-N-BITS" "SAETP-TYPECODE" "SAETP-PRIMITIVE-TYPE-NAME"
+            "SAETP-N-PAD-ELEMENTS" "SAETP-SPECIFIER"
+            "SAETP-COMPLEX-TYPECODE" "SAETP-IMPORTANCE"
+            "*SPECIALIZED-ARRAY-ELEMENT-TYPE-PROPERTIES*"
             "SANCTIFY-FOR-EXECUTION"
              "SAP-POINTER-SLOT" "SAP-REG-SC-NUMBER" "SAP-SIZE"
              "SAP-STACK-SC-NUMBER" "SAP-WIDETAG"
@@ -2009,7 +2040,7 @@ structure representations"
              "SIMPLE-ARRAY-SIGNED-BYTE-32-WIDETAG"
              "SIMPLE-ARRAY-SIGNED-BYTE-8-WIDETAG"
              "SIMPLE-BIT-VECTOR-WIDETAG"
-             "SIMPLE-STRING-WIDETAG"
+             "SIMPLE-BASE-STRING-WIDETAG"
             "SIMPLE-VECTOR-WIDETAG" "SINGLE-FLOAT-BIAS"
              "SINGLE-FLOAT-DIGITS" "SINGLE-FLOAT-EXPONENT-BYTE"
              "SINGLE-FLOAT-HIDDEN-BIT" "SINGLE-FLOAT-NORMAL-EXPONENT-MAX"
@@ -2055,7 +2086,7 @@ structure representations"
              "WEAK-POINTER-BROKEN-SLOT" "WEAK-POINTER-NEXT-SLOT"
              "WEAK-POINTER-SIZE" "WEAK-POINTER-WIDETAG"
             "WEAK-POINTER-VALUE-SLOT"
-             "WORD" "N-WORD-BITS" "N-WORD-BYTES"
+             "WORD" "N-WORD-BITS" "N-WORD-BYTES" "N-MACHINE-WORD-BITS"
             "WORD-REG-SC-NUMBER" "WORD-SHIFT"
              "ZERO-SC-NUMBER"))