0.8.0.51:

[sbcl.git] / package-data-list.lisp-expr

diff --git a/package-data-list.lisp-expr b/package-data-list.lisp-expr
index 1f7fc50..193f46e 100644 (file)
--- a/package-data-list.lisp-expr
+++ b/package-data-list.lisp-expr
@@ -499,12 +499,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 +543,11 @@ 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"
+
             ;; 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 +630,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"
@@ -702,7 +705,7 @@ retained, possibly temporariliy, because it might be used internally."
              "SIMPLE-STYLE-WARNING"
             "SPECIAL-FORM-FUNCTION"
              "STYLE-WARN"
-
+            
              ;; bootstrapping magic, to make things happen both in
              ;; the cross-compilation host compiler's environment and
              ;; in the cross-compiler's environment
@@ -874,6 +877,7 @@ retained, possibly temporariliy, because it might be used internally."
              "POSITIVE-PRIMEP"
              "EVAL-IN-LEXENV"
             "DEBUG-NAMIFY"
+             "FORCE" "DELAY" "PROMISE-READY-P"
 
              ;; These could be moved back into SB!EXT if someone has
              ;; compelling reasons, but hopefully we can get by
@@ -1071,14 +1075,16 @@ is a good idea, but see SB-SYS re. blurring of boundaries."
              "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" 
+             "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"
@@ -1252,7 +1258,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-="
@@ -1309,12 +1316,12 @@ 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"
+            "DD-INCLUDE" "SLOT-SETTER-LAMBDA-FORM"
              "%IMAGPART" "DSD-ACCESSOR-NAME"
-             "%CODE-DEBUG-INFO" "DSD-%NAME"
+             "%CODE-DEBUG-INFO"
              "LAYOUT-CLASSOID" "LAYOUT-INVALID"
              "%SIMPLE-FUN-NAME" "DSD-TYPE" "%INSTANCEP"
              "DEFSTRUCT-SLOT-DESCRIPTION" "%SIMPLE-FUN-ARGLIST"
@@ -1369,9 +1376,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"
             
@@ -1393,6 +1401,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