#s(sb-cold:package-data
:name "SB!IMPL"
:doc "private: a grab bag of implementation details"
- :use ("CL" "SB!EXT" "SB!INT" "SB!SYS" "SB!DEBUG" "SB!KERNEL" "SB!BIGNUM"
- "SB!GRAY"))
+ :use ("CL" "SB!ALIEN" "SB!BIGNUM" "SB!C-CALL" "SB!DEBUG" "SB!EXT"
+ "SB!GRAY" "SB!INT" "SB!KERNEL" "SB!SYS"))
;; FIXME: It seems to me that this could go away, with its contents moved
;; into SB!KERNEL, like the implementation of the rest of the class system.
:reexport ("LOAD-FOREIGN" "LOAD-1-FOREIGN" "WEAK-POINTER-P")
:export (;; Information about how the program was invoked is
;; nonstandard but very useful.
- "*POSIX-ARGV*" "POSIX-GETENV"
+ "*POSIX-ARGV*" "POSIX-GETENV" "POSIX-ENVIRON"
;; People have various good reasons to mess with the GC.
"*AFTER-GC-HOOKS*" "*BEFORE-GC-HOOKS*"
"DEFINE-HASH-TABLE-TEST"
"*GC-INHIBIT-HOOK*"
+ ;; compatibility hacks for old-style CMU CL data formats
+ "UNIX-ENVIRONMENT-CMUCL-FROM-SBCL"
+ "UNIX-ENVIRONMENT-SBCL-FROM-CMUCL"
+
;; not used any more, I think -- WHN 19991206
#+nil
("SERVE-BUTTON-PRESS"
"BIT-INDEX" "BOGUS-ARGUMENT-TO-VALUES-LIST-ERROR"
"BOOLE-CODE"
"BYTE-SPECIFIER" "CALLABLE" "CASE-BODY-ERROR"
+ "CHARPOS"
"CHECK-FOR-CIRCULARITY" "CHECK-TYPE-ERROR"
+ "CLOSED-FLAME"
"CODE-COMPONENT" "CODE-COMPONENT-P"
"CODE-DEBUG-INFO" "CODE-HEADER-REF" "CODE-HEADER-SET"
"CODE-INSTRUCTIONS" "COERCE-TO-BIT-VECTOR" "COERCE-TO-FUNCTION"
"FLOAT-EXPONENT" "FLOAT-FORMAT-DIGITS" "FLOAT-FORMAT-NAME"
"FLOAT-FORMAT-MAX" "FLOATING-POINT-EXCEPTION"
"FORM" "FUNCALLABLE-INSTANCE-P"
- "FUNCTION-CODE-HEADER" "FUNCTION-TYPE"
+ "FUNCTION-CODE-HEADER" "FUNCTION-DOC"
+ "FUNCTION-TYPE"
"FUNCTION-TYPE-ALLOWP"
"FUNCTION-TYPE-KEYP" "FUNCTION-TYPE-KEYWORDS"
"FUNCTION-TYPE-NARGS" "FUNCTION-TYPE-OPTIONAL"
"HAIRY-DATA-VECTOR-REF" "HAIRY-DATA-VECTOR-SET" "HAIRY-TYPE"
"HAIRY-TYPE-CHECK-TEMPLATE-NAME" "HAIRY-TYPE-SPECIFIER"
"HANDLE-CIRCULARITY" "IGNORE-IT"
+ "ILL-BIN" "ILL-BOUT" "ILL-IN" "ILL-OUT"
"INDEX-TOO-LARGE-ERROR" "INTEGER-DECODE-DOUBLE-FLOAT"
"INTEGER-DECODE-LONG-FLOAT" "INTEGER-DECODE-SINGLE-FLOAT"
"INTERNAL-ERROR" "INTERNAL-TIME"
"KEY-INFO-P" "KEY-INFO-TYPE"
"LAYOUT-DEPTHOID"
"LAYOUT-INVALID-ERROR" "LEXENV"
+ "LINE-LENGTH"
+ "LISP-STREAM"
+ "LISP-STREAM-BIN" "LISP-STREAM-BOUT"
+ "LISP-STREAM-IN" "LISP-STREAM-IN-BUFFER"
+ "LISP-STREAM-IN-INDEX"
+ "LISP-STREAM-MISC" "LISP-STREAM-N-BIN"
+ "LISP-STREAM-OUT" "LISP-STREAM-SOUT"
"LIST-TO-SIMPLE-STRING*" "LIST-TO-BIT-VECTOR*"
"LIST-TO-VECTOR*"
"LONG-FLOAT-EXPONENT" "LONG-FLOAT-EXP-BITS"
"LONG-FLOAT-HIGH-BITS"
"LONG-FLOAT-LOW-BITS" "LONG-FLOAT-MID-BITS" "LONG-FLOAT-P"
+ "LONG-FLOAT-RADIX" "LONG-WORDS"
"LRA" "LRA-CODE-HEADER" "LRA-P"
"MAKE-ALIEN-TYPE-TYPE" "MAKE-ARGS-TYPE"
"MAKE-ARRAY-HEADER" "MAKE-ARRAY-TYPE" "MAKE-CONS-TYPE"
"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"
"OBJECT-NOT-VECTOR-ERROR" "OBJECT-NOT-WEAK-POINTER-ERROR"
"ODD-KEYWORD-ARGUMENTS-ERROR"
"OUTPUT-OBJECT" "OUTPUT-UGLY-OBJECT"
+ "PACKAGE-DOC-STRING"
+ "PACKAGE-HASHTABLE-SIZE" "PACKAGE-HASHTABLE-FREE"
+ "PACKAGE-INTERNAL-SYMBOLS" "PACKAGE-EXTERNAL-SYMBOLS"
"PARSE-DEFMACRO" "PARSE-LAMBDA-LIST" "PARSE-UNKNOWN-TYPE"
"PARSE-UNKNOWN-TYPE-SPECIFIER"
- "PATHNAME-DESIGNATOR" "PUNT-IF-TOO-LONG"
+ "PATHNAME-DESIGNATOR" "PUNT-PRINT-IF-TOO-LONG"
"READER-PACKAGE-ERROR"
#!+gengc "*SAVED-STATE-CHAIN*"
"SCALE-DOUBLE-FLOAT" "SCALE-LONG-FLOAT"
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")
- :import-from (("SB!KERNEL" "FUNCALLABLE-INSTANCE-P" "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"))
:reexport ("ADD-METHOD" "ALLOCATE-INSTANCE"
"COMPUTE-APPLICABLE-METHODS"
"ENSURE-GENERIC-FUNCTION"
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
"GET-PAGE-SIZE" "GET-SYSTEM-INFO"
"IGNORE-INTERRUPT"
"INT-SAP" "INVALIDATE-DESCRIPTOR" "IO-TIMEOUT"
- "LISP-STREAM" "LONG-FLOAT-RADIX" "LONG-WORDS"
"MACRO" "MAKE-FD-STREAM" "MAKE-OBJECT-SET" "MAP-PORT"
"NATURALIZE-BOOLEAN" "NATURALIZE-INTEGER"
"NULL-TERMINATED-STRING" "OBJECT-SET-OPERATION"
This package only tries to implement what happens to be
needed by the current implementation of SBCL, and makes
no guarantees of interface stability."
- :use ("CL" "SB!ALIEN" "SB!C-CALL" "SB!SYS" "SB!EXT" "SB!INT")
+ :use ("CL" "SB!ALIEN" "SB!C-CALL" "SB!EXT" "SB!INT" "SB!SYS")
:export ("CADDR-T" "D-INO" "D-NAME" "D-NAMLEN" "D-OFF" "D-RECLEN"
"DADDR-T" "DEV-T" "DIRECT" "EXECGRP" "EXECOTH" "EXECOWN" "F-DUPFD"
"F-GETFD" "F-GETFL" "F-GETOWN" "F-SETFD" "F-SETFL" "F-SETOWN"
projects / sbcl.git / blobdiff