0.6.10.23:

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

diff --git a/package-data-list.lisp-expr b/package-data-list.lisp-expr
index 762ce26..996d78d 100644 (file)
--- a/package-data-list.lisp-expr
+++ b/package-data-list.lisp-expr
@@ -674,7 +674,7 @@ retained, possibly temporariliy, because it might be used internally."
              "*SETF-FDEFINITION-HOOK*"
 
              ;; non-standard but widely useful user-level functions..
-             "ASSQ" "DELQ" "MEMQ"
+             "ASSQ" "DELQ" "MEMQ" "POSQ" "NEQ"
             "%FIND-PACKAGE-OR-LOSE" "FIND-UNDELETED-PACKAGE-OR-LOSE"
              "SANE-PACKAGE"
              "CIRCULAR-LIST-P"
@@ -682,7 +682,7 @@ retained, possibly temporariliy, because it might be used internally."
             ;; ..and macros..
              "COLLECT"
              "DO-ANONYMOUS" "DOHASH" "DOVECTOR"
-             "ITERATE"
+             "NAMED-LET"
              "LETF" "LETF*"
              "ONCE-ONLY"
              "DEFENUM"
@@ -723,11 +723,6 @@ retained, possibly temporariliy, because it might be used internally."
              ;; FIXME: maybe belongs in %KERNEL with other typesystem stuff?
              "CONSTANT-ARGUMENT"
 
-             ;; FIXME: Maybe this isn't used any more? And if it is,
-             ;; it probably needs a better name, since SPECIAL things
-             ;; are such a nice source of sneaky bugs.
-             "E"
-
              ;; various internal defaults
              "*DEFAULT-PACKAGE-USE-LIST*"
              "DEFAULT-INIT-CHAR"
@@ -818,8 +813,8 @@ retained, possibly temporariliy, because it might be used internally."
 
  #s(sb-cold:package-data
     :name "SB!ITERATE"
-    :doc "private: implementation of an iteration facility used by PCL"
-    :use ("CL" "SB!WALKER")
+    :doc "private: an iteration facility used to implement PCL"
+    :use ("CL" "SB!WALKER" "SB!INT" "SB!EXT")
     :export ("ITERATE" "ITERATE*" "GATHERING" "GATHER"
              "WITH-GATHERING" "INTERVAL" "ELEMENTS"
              "LIST-ELEMENTS" "LIST-TAILS" "PLIST-ELEMENTS"
@@ -997,7 +992,10 @@ is a good idea, but see SB-SYS for blurring of boundaries."
              "MAKE-MEMBER-TYPE" "MAKE-NAMED-TYPE"
              "MAKE-NULL-LEXENV" "MAKE-NUMERIC-TYPE"
              "MAKE-SINGLE-FLOAT" "MAKE-SPECIALIZABLE-ARRAY"
-             "%MAKE-INSTANCE" "MAKE-UNION-TYPE" "MAKE-VALUES-TYPE"
+             "%MAKE-INSTANCE"
+             "MAKE-INTERSECTION-TYPE-OR-SOMETHING" 
+             "MAKE-UNION-TYPE-OR-SOMETHING" 
+             "MAKE-VALUES-TYPE"
              "MAYBE-GC" "MEMBER-TYPE" "MEMBER-TYPE-MEMBERS"
              "MEMBER-TYPE-P" "MERGE-BITS"
              "DEFMACRO-MUNDANELY" "MUTATOR-SELF"
@@ -1019,6 +1017,11 @@ is a good idea, but see SB-SYS for blurring of boundaries."
              "OBJECT-NOT-COMPLEX-LONG-FLOAT-ERROR"
              "OBJECT-NOT-COMPLEX-DOUBLE-FLOAT-ERROR"
              "OBJECT-NOT-COMPLEX-RATIONAL-ERROR"
+             ;; FIXME: It's confusing using "complex" to mean
+             ;; both "not on the real number line" and "not of
+             ;; a SIMPLE-ARRAY nature". Perhaps we could rename
+             ;; all the uses in the second sense as "hairy" instead?
+             "OBJECT-NOT-COMPLEX-VECTOR-ERROR"
              "OBJECT-NOT-CONS-ERROR"
              "OBJECT-NOT-DOUBLE-FLOAT-ERROR" "OBJECT-NOT-FIXNUM-ERROR"
              "OBJECT-NOT-FLOAT-ERROR" "OBJECT-NOT-FUNCTION-ERROR"
@@ -1279,12 +1282,18 @@ is a good idea, but see SB-SYS for blurring of boundaries."
 extensions, but even they are not guaranteed to be present in
 later versions of SBCL, and the other stuff in here is
 definitely not guaranteed to be present in later versions of SBCL."
-    :use ("CL" "SB!ITERATE" "SB!WALKER")
+    ;; FIXME: SB-PCL should probably USE-PACKAGE SB-KERNEL, since SB-PCL
+    ;; is built on SB-KERNEL, and in the absence of USE-PACKAGE, it ends
+    ;; up using a thundering herd of explicit prefixes to get to
+    ;; SB-KERNEL symbols. However, it'll probably be too messy to do
+    ;; this until the duplicate SB-PCL:CLASS/CL:CLASS hierarchy kludge
+    ;; is unscrewed, since until it is there are too many things which
+    ;; conflict between the two packages.
+    :use ("CL" "SB!ITERATE" "SB!WALKER" "SB!INT" "SB!EXT")
     :import-from (("SB!KERNEL" "FUNCALLABLE-INSTANCE-P" "FUNCTION-DOC"
                    "PACKAGE-DOC-STRING"
                    "PACKAGE-HASHTABLE-SIZE" "PACKAGE-HASHTABLE-FREE"
-                   "PACKAGE-INTERNAL-SYMBOLS" "PACKAGE-EXTERNAL-SYMBOLS"
-                   "SB!INT" "SB!EXT"))
+                   "PACKAGE-INTERNAL-SYMBOLS" "PACKAGE-EXTERNAL-SYMBOLS"))
     :reexport ("ADD-METHOD" "ALLOCATE-INSTANCE"
                "COMPUTE-APPLICABLE-METHODS"
                "ENSURE-GENERIC-FUNCTION"
@@ -1377,7 +1386,7 @@ definitely not guaranteed to be present in later versions of SBCL."
 necessary for system interfacing\" (said cmu-user.tex at the time
 of the SBCL code fork). That probably was and is a good idea, but in
 practice, the distinctions between this package and SB-KERNEL
-and even SB-VM have become somewhat blurred over the years."
+and even SB-VM seem to have become somewhat blurred over the years."
     :use ("CL" "SB!EXT" "SB!INT")
     :export ("%ASSEMBLER-CODE-TYPE" "%BIND-ALIGNED-SAP"
              ;; FIXME: %PRIMITIVE shouldn't be here. (I now know that %SYS
@@ -1755,7 +1764,7 @@ structure representations"
  #s(sb-cold:package-data
     :name "SB!WALKER"
     :doc "internal: a code walker used by PCL"
-    :use ("CL")
+    :use ("CL" "SB!INT" "SB!EXT")
     :export ("DEFINE-WALKER-TEMPLATE" "WALK-FORM"
              "*WALK-FORM-EXPAND-MACROS-P*" 
              "VARIABLE-LEXICAL-P" "VARIABLE-SPECIAL-P"