X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=package-data-list.lisp-expr;h=eca3957da6e42a613cc0bf6a4dc1e8ca31f65060;hb=5fc1ec5b716d89f5018bc159a88f82cb2077b7e6;hp=e5a878e0918b1f7f5fd102bb963e5881ef2d1fc5;hpb=88cc2f72774202503588331fddd1592ae8546de1;p=sbcl.git diff --git a/package-data-list.lisp-expr b/package-data-list.lisp-expr index e5a878e..eca3957 100644 --- a/package-data-list.lisp-expr +++ b/package-data-list.lisp-expr @@ -221,6 +221,7 @@ of SBCL which maintained the CMU-CL-style split into two packages.)" "ALLOC-ALIEN-STACK-SPACE" "ALLOC-NUMBER-STACK-SPACE" "ALLOCATE-CODE-OBJECT" "ALLOCATE-FRAME" "ALLOCATE-DYNAMIC-CODE-OBJECT" "ALLOCATE-FULL-CALL-FRAME" + "ALWAYS-TRANSLATABLE" "ANY" "ARG-COUNT-ERROR" "ASSEMBLE-FILE" "ATTRIBUTES" "ATTRIBUTES-INTERSECTION" "ATTRIBUTES-UNION" "ATTRIBUTES=" "BIND" @@ -570,7 +571,6 @@ like *STACK-TOP-HINT* and unsupported stuff like *TRACED-FUN-LIST*." ;; People have various good reasons to mess with the GC. "*AFTER-GC-HOOKS*" - "*GC-NOTIFY-AFTER*" "*GC-NOTIFY-BEFORE*" "*GC-NOTIFY-STREAM*" "BYTES-CONSED-BETWEEN-GCS" "GC" "GC-OFF" "GC-ON" "GET-BYTES-CONSED" "*GC-RUN-TIME*" @@ -641,19 +641,12 @@ like *STACK-TOP-HINT* and unsupported stuff like *TRACED-FUN-LIST*." ;; a year or so it can go away completely. "DEF-SOURCE-CONTEXT" - ;; FIXME: These seem like the right thing, but are they - ;; consistent with ANSI? (And actually maybe they're not - ;; quite the right thing; it might be better to also do - ;; WITH-STANDARD-IO-SYNTAX or something.) - "*ERROR-PRINT-LENGTH*" "*ERROR-PRINT-LEVEL*" "*ERROR-PRINT-LINES*" - ;; extended declarations.. "FREEZE-TYPE" "INHIBIT-WARNINGS" "MAYBE-INLINE" ;; ..and variables to control compiler policy "*INLINE-EXPANSION-LIMIT*" - "*USE-IMPLEMENTATION-TYPES*" "*DERIVE-FUNCTION-TYPES*" ;; ..and inspector of compiler policy @@ -838,6 +831,8 @@ retained, possibly temporariliy, because it might be used internally." "CHARACTER-DECODING-ERROR" "CHARACTER-DECODING-ERROR-OCTETS" "CHARACTER-ENCODING-ERROR" "CHARACTER-ENCODING-ERROR-CODE" "STREAM-DECODING-ERROR" "STREAM-ENCODING-ERROR" + "C-STRING-ENCODING-ERROR" "C-STRING-ENCODING-ERROR-EXTERNAL-FORMAT" + "C-STRING-DECODING-ERROR" "C-STRING-DECODING-ERROR-EXTERNAL-FORMAT" "ATTEMPT-RESYNC" "FORCE-END-OF-FILE" ;; bootstrapping magic, to make things happen both in @@ -858,6 +853,7 @@ retained, possibly temporariliy, because it might be used internally." "MAKE-TRIVIAL-DEFAULT-PATHNAME" "PHYSICALIZE-PATHNAME" "SANE-DEFAULT-PATHNAME-DEFAULTS" + "SBCL-HOMEDIR-PATHNAME" ;; PCOUNTERs "FASTBIG-INCF-PCOUNTER-OR-FIXNUM" @@ -875,7 +871,7 @@ retained, possibly temporariliy, because it might be used internally." "ADJUST-LIST" "%FIND-PACKAGE-OR-LOSE" "FIND-UNDELETED-PACKAGE-OR-LOSE" "SANE-PACKAGE" - "CYCLIC-LIST-P" + "MAYBE-CYCLIC-P" "COMPOUND-OBJECT-P" "SWAPPED-ARGS-FUN" "AND/TYPE" "NOT/TYPE" @@ -888,6 +884,8 @@ retained, possibly temporariliy, because it might be used internally." "NTH-BUT-WITH-SANE-ARG-ORDER" "DEPRECATION-WARNING" "BIT-VECTOR-=" + "READ-EVALUATED-FORM" + "MAKE-UNPRINTABLE-OBJECT" ;; ..and macros.. "COLLECT" @@ -1460,6 +1458,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries." "UNKNOWN-TYPE-SPECIFIER" "UNSEEN-THROW-TAG-ERROR" ;; FIXME: 32/64-bit issues "UNSIGNED-BYTE-32-P" "UNSIGNED-BYTE-64-P" + "UPDATE-OBJECT-LAYOUT-OR-INVALID" "VALUE-CELL-REF" "VALUE-CELL-SET" "VALUES-SPECIFIER-TYPE" "VALUES-SPECIFIER-TYPE-CACHE-CLEAR" "VALUES-SUBTYPEP" "VALUES-TYPE" "VALUES-TYPE-ERROR" "VALUES-TYPE-IN" @@ -2093,6 +2092,7 @@ structure representations" :export ("*ASSEMBLY-UNIT-LENGTH*" "*PRIMITIVE-OBJECTS*" "AFTER-BREAKPOINT-TRAP" + "*ALLOC-SIGNAL*" "ANY-REG-SC-NUMBER" "ARRAY-DATA-SLOT" "ARRAY-DIMENSIONS-OFFSET" "ARRAY-DISPLACED-P-SLOT" "ARRAY-DISPLACEMENT-SLOT" "ARRAY-ELEMENTS-SLOT" "ARRAY-FILL-POINTER-P-SLOT" @@ -2356,4 +2356,6 @@ SBCL itself" "GET-LAST-ERROR" "GET-OSFHANDLE" "HANDLE" "HANDLE-CLEAR-INPUT" "HANDLE-LISTEN" "INT-PTR" "INVALID-HANDLE" "MILLISLEEP" "PEEK-CONSOLE-INPUT" - "PEEK-NAMED-PIPE" "READ-FILE" "WRITE-FILE"))) + "PEEK-NAMED-PIPE" "READ-FILE" "WRITE-FILE" + + "GET-PROCESS-TIMES")))