- :name "SB!C-CALL"
- ;; FIXME: Why not just put this stuff into SB-ALIEN? Or maybe
- ;; just glom this and SB-ALIEN together into SB-FFI?
- :doc "public: some types used with ALIENs"
- :use ("CL" "SB!SYS" "SB!ALIEN-INTERNALS" "SB!ALIEN" "SB!INT" "SB!EXT")
- :reexport ("FLOAT" "CHAR")
- :export ("C-STRING" "DOUBLE" "INT" "LONG"
- "SHORT" "UNSIGNED-CHAR" "UNSIGNED-INT"
- "UNSIGNED-LONG" "UNSIGNED-SHORT" "VOID"))
-
- #!+sb-dyncount
- #s(sb-cold:package-data
- :name "SB!DYNCOUNT"
- :doc "private: some somewhat-stale code for collecting runtime statistics"
- :use ("CL" "SB!ALIEN-INTERNALS" "SB!ALIEN" "SB!BIGNUM"
- "SB!EXT" "SB!INT" "SB!KERNEL" "SB!ASSEM" "SB!SYS")
- :export ("*COLLECT-DYNAMIC-STATISTICS*" "COUNT-ME"
- "DYNCOUNT-INFO-COUNTS" "DYNCOUNT-INFO-COSTS"
- "IR2-COMPONENT-DYNCOUNT-INFO"
- "DYNCOUNT-INFO" "DYNCOUNT-INFO-P"))
-
- ;; This package is a grab bag for things which used to be internal
- ;; symbols in package COMMON-LISP. Lots of these symbols are accessed
- ;; with explicit SB!IMPL:: prefixes in the code. It would be nice to
- ;; reduce the use of this practice, so if symbols from here which are
- ;; accessed that way are found to belong more appropriately in
- ;; an existing package (e.g. KERNEL or SYS or EXT) or a new package
- ;; (e.g. something to collect together all the FOP stuff), I
- ;; (WHN 19990223) encourage maintainers to move them there..
- ;;
- ;; ..except that it's getting so big and crowded that maybe it
- ;; should be split up, too.
- #s(sb-cold:package-data
- :name "SB!IMPL"
- :doc "private: a grab bag of implementation details"
- :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.
-;; #s(sb-cold:package-data
-;; :name "SB!CONDITIONS"
-;; :doc "private: the implementation of the condition system"
-;; :use ("CL" "SB!EXT" "SB!INT" "SB!KERNEL"))
-
- #s(sb-cold:package-data