X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;ds=sidebyside;f=package-data-list.lisp-expr;h=79759bfab19cae3da111eff82b5b412121ab314d;hb=171fde84561e232b8af8c05b82dfe8a8f9e08340;hp=54430d77c3dfdb451c3ebdbc419148af4dce7ec6;hpb=1a61f069111cb6f7263852b73eea1bd8cda9ef68;p=sbcl.git diff --git a/package-data-list.lisp-expr b/package-data-list.lisp-expr index 54430d7..79759bf 100644 --- a/package-data-list.lisp-expr +++ b/package-data-list.lisp-expr @@ -712,6 +712,9 @@ like *STACK-TOP-HINT* and unsupported stuff like *TRACED-FUN-LIST*." ;; and one for controlling same at runtime "*MUFFLED-WARNINGS*" + ;; specification which print errors to ignore ala *break-on-signal* + "*SUPPRESS-PRINT-ERRORS*" + ;; extended declarations.. "ALWAYS-BOUND" "FREEZE-TYPE" "GLOBAL" "INHIBIT-WARNINGS" "MAYBE-INLINE" @@ -1034,6 +1037,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" @@ -1383,7 +1387,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" @@ -2367,7 +2371,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"