"VALUES" "*")
:export ("ADDR" "ALIEN" "ALIEN-FUNCALL" "ALIEN-SAP" "ALIEN-SIZE"
"CAST"
- "DEF-ALIEN-ROUTINE" "DEF-ALIEN-TYPE"
- "DEF-ALIEN-VARIABLE" "DEF-BUILTIN-ALIEN-TYPE"
+ "DEFINE-ALIEN-ROUTINE" "DEFINE-ALIEN-TYPE" "DEFINE-ALIEN-VARIABLE"
+
+ ;; FIXME: These old names don't match the DEFFOO - vs. -
+ ;; DEFINE-FOO convention used in the ANSI spec, and so
+ ;; were deprecated in sbcl-0.pre7, ca. 2001-12-12. After
+ ;; a year or so they can go away completely.
+ "DEF-ALIEN-ROUTINE" "DEF-ALIEN-TYPE" "DEF-ALIEN-VARIABLE"
+
"DEREF"
"ENUM" "EXTERN-ALIEN"
"FREE-ALIEN"
"ALIEN-VALUES-TYPE-VALUES" "ALIGN-OFFSET" "COMPUTE-ALIEN-REP-TYPE"
"COMPUTE-DEPORT-LAMBDA" "COMPUTE-DEPOSIT-LAMBDA"
"COMPUTE-EXTRACT-LAMBDA" "COMPUTE-LISP-REP-TYPE"
- "COMPUTE-NATURALIZE-LAMBDA" "DEF-ALIEN-TYPE-CLASS"
- "DEF-ALIEN-TYPE-METHOD" "DEF-ALIEN-TYPE-TRANSLATOR" "DEPORT"
+ "COMPUTE-NATURALIZE-LAMBDA" "DEFINE-ALIEN-TYPE-CLASS"
+ "DEFINE-ALIEN-TYPE-METHOD" "DEFINE-ALIEN-TYPE-TRANSLATOR" "DEPORT"
"DEPOSIT-ALIEN-VALUE" "DISPOSE-LOCAL-ALIEN" "EXTRACT-ALIEN-VALUE"
"HEAP-ALIEN-INFO" "HEAP-ALIEN-INFO-P" "HEAP-ALIEN-INFO-SAP-FORM"
"HEAP-ALIEN-INFO-TYPE" "INVOKE-ALIEN-TYPE-METHOD" "LOCAL-ALIEN"
"DEALLOC-NUMBER-STACK-SPACE" "DEF-BOOLEAN-ATTRIBUTE"
"DEF-IR1-TRANSLATOR"
"!DEF-PRIMITIVE-TYPE" "!DEF-PRIMITIVE-TYPE-ALIAS"
- "DEF-SOURCE-TRANSFORM" "!DEF-VM-SUPPORT-ROUTINE"
+ "DEFINE-SOURCE-TRANSFORM" "!DEF-VM-SUPPORT-ROUTINE"
"DEFINE-ASSEMBLY-ROUTINE" "DEFINE-MOVE-FUNCTION"
"DEFINE-MOVE-VOP" "DEFINE-STORAGE-BASE"
"DEFINE-STORAGE-CLASS" "DEFINE-VOP"
"DEFTRANSFORM" "DERIVE-TYPE"
"ENTRY-NODE-INFO-NLX-TAG" "ENTRY-NODE-INFO-ST-TOP"
"PHYSENV-DEBUG-LIVE-TN" "PHYSENV-LIVE-TN"
- "FAST-SYMBOL-FUNCTION" "FAST-SYMBOL-VALUE" "FOLDABLE"
+ "FAST-SYMBOL-VALUE" "FOLDABLE"
"FORCE-TN-TO-STACK"
"GET-VECTOR-SUBTYPE"
"HALT"
"BREAKPOINT-KIND" "BREAKPOINT-P" "BREAKPOINT-WHAT" "CODE-LOCATION"
"CODE-LOCATION-DEBUG-BLOCK" "CODE-LOCATION-DEBUG-FUN"
"CODE-LOCATION-DEBUG-SOURCE" "CODE-LOCATION-FORM-NUMBER"
- "CODE-LOCATION-P" "CODE-LOCATION-TOP-LEVEL-FORM-OFFSET"
+ "CODE-LOCATION-P" "CODE-LOCATION-TOPLEVEL-FORM-OFFSET"
"CODE-LOCATION-UNKNOWN-P" "CODE-LOCATION=" "DEACTIVATE-BREAKPOINT"
"DEBUG-BLOCK" "DEBUG-BLOCK-ELSEWHERE-P" "DEBUG-BLOCK-P"
"DEBUG-BLOCK-SUCCESSORS" "DEBUG-CONDITION" "DEBUG-ERROR"
"DELETE-BREAKPOINT" "DO-BLOCKS"
"DO-DEBUG-BLOCK-LOCATIONS" "DO-DEBUG-FUN-BLOCKS"
"DO-DEBUG-FUN-VARIABLES"
- "FORM-NUMBER-TRANSLATIONS" "FRAME" "FRAME-CATCHES"
- "FRAME-CODE-LOCATION" "FRAME-DEBUG-FUN" "FRAME-DOWN"
+ "FORM-NUMBER-TRANSLATIONS"
+ "FRAME" "FRAME-CATCHES" "FRAME-CODE-LOCATION"
+ "FRAME-DEBUG-FUN" "FRAME-DOWN"
"FRAME-FUN-MISMATCH" "FRAME-NUMBER" "FRAME-P" "FRAME-UP"
"FUN-DEBUG-FUN" "FUN-END-COOKIE-VALID-P"
"INVALID-CONTROL-STACK-POINTER" "INVALID-VALUE"
"FASL-DUMP-COLD-LOAD-FORM" "FASL-DUMP-COMPONENT"
"FASL-DUMP-COLD-FSET"
"FASL-DUMP-LOAD-TIME-VALUE" "FASL-DUMP-LOAD-TIME-VALUE-LAMBDA"
- "FASL-DUMP-SOURCE-INFO" "FASL-DUMP-TOP-LEVEL-LAMBDA-CALL"
+ "FASL-DUMP-SOURCE-INFO" "FASL-DUMP-TOPLEVEL-LAMBDA-CALL"
"FASL-NOTE-HANDLE-FOR-CONSTANT"
"FASL-OUTPUT" "FASL-OUTPUT-P"
"FASL-OUTPUT-ENTRY-TABLE" "FASL-OUTPUT-STREAM"
;; and for dedicated users who really want to customize
;; error reporting, we have
- "DEF-SOURCE-CONTEXT"
+ "DEFINE-SOURCE-CONTEXT"
+
+ ;; 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
+ ;; 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
;; ..and variables to control compiler policy
"*INLINE-EXPANSION-LIMIT*"
"*USE-IMPLEMENTATION-TYPES*"
- "*BYTE-COMPILE-TOP-LEVEL*"
- "*BYTE-COMPILE-DEFAULT*"
"*DERIVE-FUNCTION-TYPES*"
;; a special form for breaking out of our "declarations
#s(sb-cold:package-data
:name "SB!INT"
:doc
-"private: miscellaneous unsupported extensions to the ANSI spec. Most of
+"private: miscellaneous unsupported extensions to the ANSI spec. Much of
the stuff in here originated in CMU CL's EXTENSIONS package and is
retained, possibly temporariliy, because it might be used internally."
:use ("CL" "SB!ALIEN" "SB!C-CALL" "SB!GRAY" "SB!FASL" "SB!SYS")
:export ("*AFTER-SAVE-INITIALIZATIONS*" "*BEFORE-SAVE-INITIALIZATIONS*"
- "*ALL-MODIFIER-NAMES*"
- "*BACKUP-EXTENSION*"
-
;; lambda list keyword extensions
"&MORE"
;; hash mixing operations
"MIX" "MIXF"
- ;; optimization idioms
- "*OPTIMIZE-BYTE-COMPILATION*"
- "*OPTIMIZE-EXTERNAL-DESPITE-BYTE-COMPILATION*"
-
- ;; Arguably there's no one right value for the system
- ;; prompt. But Common Lisp makes it easy for you to write
- ;; your own REPL if you really care, so I'm not convinced we
- ;; need this as a supported extension.
- "*PROMPT*"
-
;; I'm not convinced that FDEFINITIONs are the ideal
;; solution, so exposing ways to peek into the system
;; seems undesirable, since it makes it harder to get
;; in the cross-compiler's environment
"DEF!MACRO" "DEF!METHOD" "DEF!STRUCT" "DEF!TYPE"
+ ;; stuff for hinting to the compiler
+ "NAMED-LAMBDA"
+
;; other variations on DEFFOO stuff useful for bootstrapping
;; and cross-compiling
"DEFMACRO-MUNDANELY"
"PSXHASH"
"%BREAK"
"NTH-BUT-WITH-SANE-ARG-ORDER"
+ "DEPRECATION-WARNING"
;; ..and macros..
"COLLECT"
"DO-ANONYMOUS" "DOHASH" "DOVECTOR"
- "NAMED-LAMBDA"
"NAMED-LET"
"ONCE-ONLY"
"DEFENUM"
"DEFPRINTER"
- "AVER" "AVER-TYPE" "ENFORCE-TYPE"
+ "AVER" "ENFORCE-TYPE"
;; ..and DEFTYPEs..
"INDEX"
;; encapsulation
"ARGUMENT-LIST"
"BASIC-DEFINITION"
- "ENCAPSULATE" "ENCAPSULATED-DEFINITION" "ENCAPSULATED-P"
+ "ENCAPSULATE" "ENCAPSULATED-P"
"UNENCAPSULATE"
;; various CHAR-CODEs
;; time
"FORMAT-DECODED-TIME"
"FORMAT-UNIVERSAL-TIME"
- "PARSE-TIME"
;; indenting
"MAKE-INDENTING-STREAM"
"COLD-FSET"
"!DEFUN-FROM-COLLECTED-COLD-INIT-FORMS"))
- #s(sb-cold:package-data
- :name "SB!ITERATE"
- :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"
- "EACHTIME" "WHILE" "UNTIL" "COLLECTING" "JOINING"
- "MAXIMIZING" "MINIMIZING" "SUMMING"
- "*ITERATE-WARNINGS*"))
-
;; FIXME: This package is awfully huge. It'd probably be good to
;; split it. There's at least one natural way to split it: the
;; implementation of the Lisp type system (e.g. TYPE-INTERSECTION and
"%DOUBLE-FLOAT" "%DPB" "%EXP" "%EXPM1"
"%FIND-POSITION" "%FIND-POSITION-VECTOR-MACRO"
"%FIND-POSITION-IF" "%FIND-POSITION-IF-VECTOR-MACRO"
+ "%FUN-DOC" "%FUN-NAME"
"%HYPOT" "%LDB"
"%LOG" "%LOGB" "%LOG10" "%LOG1P" "%LONG-FLOAT"
"%MAKE-COMPLEX" "%MAKE-FUNCALLABLE-INSTANCE" "%MAKE-RATIO"
"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" "FUNCTION-DOC"
+ "FUN-CODE-HEADER"
"FUN-TYPE" "FUN-TYPE-ALLOWP"
"FUN-TYPE-KEYP" "FUN-TYPE-KEYWORDS"
"FUN-TYPE-NARGS" "FUN-TYPE-OPTIONAL"
"OBJECT-NOT-CONS-ERROR"
"OBJECT-NOT-DOUBLE-FLOAT-ERROR" "OBJECT-NOT-FIXNUM-ERROR"
"OBJECT-NOT-FLOAT-ERROR" "OBJECT-NOT-FUNCTION-ERROR"
- "OBJECT-NOT-FUNCTION-OR-SYMBOL-ERROR"
"OBJECT-NOT-INSTANCE-ERROR"
"OBJECT-NOT-INTEGER-ERROR"
"OBJECT-NOT-LIST-ERROR" "OBJECT-NOT-LONG-FLOAT-ERROR"
"VECTOR-TO-BIT-VECTOR*" "VECTOR-TO-SIMPLE-BIT-VECTOR*"
"VECTOR-OF-CHECKED-LENGTH-GIVEN-LENGTH"
"WITH-ARRAY-DATA"
- "WITH-CIRCULARITY-DETECTION" "WITH-TYPE-CACHES"
"WRONG-NUMBER-OF-INDICES-ERROR"
"FDEFN" "MAKE-FDEFN" "FDEFN-P"
"FDEFN-NAME" "FDEFN-FUN"
- "FDEFN-MAKUNBOUND" "%COERCE-NAME-TO-FUNCTION"
- "%COERCE-CALLABLE-TO-FUNCTION"
+ "FDEFN-MAKUNBOUND" "OUTER-FDEFN"
+ "%COERCE-CALLABLE-TO-FUN"
"FUNCTION-SUBTYPE" "*MAXIMUM-ERROR-DEPTH*"
"%SET-SYMBOL-PLIST" "INFINITE-ERROR-PROTECT"
"FIND-CALLER-NAME-AND-FRAME"
"%SET-SYMBOL-VALUE" "%SET-SYMBOL-PACKAGE"
"OUTPUT-SYMBOL-NAME"
- "FSET" "RAW-DEFINITION"
+ "%COERCE-NAME-TO-FUN"
"INVOKE-MACROEXPAND-HOOK"
"DEFAULT-STRUCTURE-PRINT"
"LAYOUT" "LAYOUT-LENGTH"
;; 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"
+ :use ("CL" "SB!INT" "SB!EXT" "SB!WALKER")
+ :import-from (("SB!KERNEL" "FUNCALLABLE-INSTANCE-P" "%FUN-DOC"
"PACKAGE-DOC-STRING"
"PACKAGE-HASHTABLE-SIZE" "PACKAGE-HASHTABLE-FREE"
"PACKAGE-INTERNAL-SYMBOLS" "PACKAGE-EXTERNAL-SYMBOLS"))
needed by the current implementation of SBCL, and makes
no guarantees of interface stability."
:use ("CL" "SB!ALIEN" "SB!C-CALL" "SB!EXT" "SB!INT" "SB!SYS")
- :export ("D-INO" "D-NAME" "D-NAMLEN" "D-OFF" "D-RECLEN"
+ :export (;; wrappers around Unix stuff to give just what Lisp needs
+ "UID-USERNAME"
+
+ ;; stuff with a one-to-one mapping to Unix constructs
+ "D-INO" "D-NAME" "D-NAMLEN" "D-OFF" "D-RECLEN"
"DEV-T" "DIRECT" "EXECGRP" "EXECOTH" "EXECOWN" "F-DUPFD"
"F-GETFD" "F-GETFL" "F-GETOWN" "F-SETFD" "F-SETFL" "F-SETOWN"
"FAPPEND" "FASYNC" "FCREAT" "FEXCL" "FIONREAD" "FNDELAY" "FTRUNC"
"CONTEXT-FLOATING-POINT-MODES" "CONTEXT-FLOAT-REGISTER"
"CONTEXT-PC" "CONTEXT-REGISTER"
"CONTROL-STACK-SC-NUMBER" "COUNT-NO-OPS"
+ "*CURRENT-CATCH-BLOCK*"
"CURRENT-DYNAMIC-SPACE-START"
"CURRENT-FLOAT-TRAP" "DEFINE-FOR-EACH-PRIMITIVE-OBJECT"
"DESCRIPTOR-REG-SC-NUMBER" "DESCRIPTOR-VS-NON-DESCRIPTOR-STORAGE"
projects / sbcl.git / blobdiff