X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=package-data-list.lisp-expr;h=36cfd9ae70f9eeba1959128b644299cae2adcd7f;hb=41bc875c0db352fb11e52e0d104e032682f49239;hp=58915b0f1d2ac61c6c505628c48b6655514c2f5c;hpb=b43491a8a0411a13535558aa1b975ae082acc1f7;p=sbcl.git diff --git a/package-data-list.lisp-expr b/package-data-list.lisp-expr index 58915b0..36cfd9a 100644 --- a/package-data-list.lisp-expr +++ b/package-data-list.lisp-expr @@ -799,6 +799,7 @@ like *STACK-TOP-HINT* and unsupported stuff like *TRACED-FUN-LIST*." "TYPEXPAND-1" "TYPEXPAND" "TYPEXPAND-ALL" "DEFINED-TYPE-NAME-P" "VALID-TYPE-SPECIFIER-P" "DELETE-DIRECTORY" + "SET-SBCL-SOURCE-LOCATION" ;; stepping interface "STEP-CONDITION" "STEP-FORM-CONDITION" "STEP-FINISHED-CONDITION" @@ -1033,6 +1034,7 @@ possibly temporariliy, because it might be used internally." "READ-EVALUATED-FORM" "MAKE-UNPRINTABLE-OBJECT" "POWER-OF-TWO-CEILING" + "PRINT-NOT-READABLE-ERROR" ;; ..and macros.. "COLLECT" @@ -1382,7 +1384,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries." "%SET-VECTOR-RAW-BITS" "%SET-SAP-REF-16" "%SET-SAP-REF-32" "%SET-SAP-REF-64" "%SET-SAP-REF-WORD" "%SET-SAP-REF-8" "%SET-SAP-REF-DOUBLE" - "%SET-SAP-REF-LONG" "%SET-SAP-REF-SAP" + "%SET-SAP-REF-LISPOBJ" "%SET-SAP-REF-LONG" "%SET-SAP-REF-SAP" "%SET-SAP-REF-SINGLE" "%SET-SIGNED-SAP-REF-16" "%SET-SIGNED-SAP-REF-32" "%SET-SIGNED-SAP-REF-64" "%SET-SIGNED-SAP-REF-WORD" @@ -2366,7 +2368,7 @@ SB-KERNEL) have been undone, but probably more remain." "SAP-INT" "SAP-REF-16" "SAP-REF-32" "SAP-REF-64" "SAP-REF-WORD" "SAP-REF-8" - "SAP-REF-DOUBLE" "SAP-REF-LONG" + "SAP-REF-DOUBLE" "SAP-REF-LISPOBJ" "SAP-REF-LONG" "SAP-REF-SAP" "SAP-REF-SINGLE" "SAP<" "SAP<=" "SAP=" "SAP>" "SAP>=" "SCRUB-CONTROL-STACK" "SERVE-ALL-EVENTS"