"*USE-IMPLEMENTATION-TYPES*"
"*BYTE-COMPILE-TOP-LEVEL*"
"*BYTE-COMPILE-DEFAULT*"
- "*DERIVE-FUNCTION-TYPES*" ; FIXME FIXME FIXME FIXME..
+ "*DERIVE-FUNCTION-TYPES*"
;; a special form for breaking out of our "declarations
;; are assertions" default
;; in the cross-compiler's environment
"DEF!MACRO" "DEF!METHOD" "DEF!STRUCT" "DEF!TYPE"
+ ;; other variations on DEFFOO stuff useful for bootstrapping
+ ;; and cross-compiling
+ "DEFMACRO-MUNDANELY"
+ "DEFCONSTANT-EQX"
+
;; messing with PATHNAMEs
"MAKE-TRIVIAL-DEFAULT-PATHNAME"
"PHYSICALIZE-PATHNAME"
"FEATUREP"
"FLUSH-STANDARD-OUTPUT-STREAMS"
"MAKE-GENSYM-LIST"
- "DEFCONSTANT-EQX"
"ABOUT-TO-MODIFY"
"PRINT-PRETTY-ON-STREAM-P"
+ "LOOKS-LIKE-NAME-OF-SPECIAL-VAR-P"
;; These could be moved back into SB!EXT if someone has
;; compelling reasons, but hopefully we can get by
:doc
"private: Theoretically this 'hides state and types used for package
integration' (said CMU CL architecture.tex) and that probably was and
-is a good idea, but see SB-SYS for blurring of boundaries."
+is a good idea, but see SB-SYS re. blurring of boundaries."
:use ("CL" "SB!ALIEN" "SB!ALIEN-INTERNALS" "SB!BIGNUM"
"SB!EXT" "SB!FASL" "SB!INT" "SB!SYS" "SB!GRAY")
:import-from (("SB!C-CALL" "VOID"))
"DOUBLE-FLOAT-INT-EXPONENT" "DOUBLE-FLOAT-LOW-BITS"
"DOUBLE-FLOAT-SIGNIFICAND"
"DOUBLE-FLOAT-P" "FLOAT-WAIT"
- "DYNAMIC-SPACE-FREE-POINTER"
+ "DYNAMIC-SPACE-FREE-POINTER" "DYNAMIC-USAGE"
"!DEFUN-FROM-COLLECTED-COLD-INIT-FORMS"
"ERROR-NUMBER-OR-LOSE" "FDEFINITION-OBJECT"
"FDOCUMENTATION" "FILENAME"
"MAKE-VALUES-TYPE"
"MAYBE-GC" "MEMBER-TYPE" "MEMBER-TYPE-MEMBERS"
"MEMBER-TYPE-P" "MERGE-BITS" "MODIFIED-NUMERIC-TYPE"
- "DEFMACRO-MUNDANELY" "MUTATOR-SELF"
+ "MUTATOR-SELF"
"NAMED-TYPE" "NAMED-TYPE-NAME" "NAMED-TYPE-P"
"NATIVE-BYTE-ORDER" "NEGATE"
"NEVER-SUBTYPEP" "NIL-FUNCTION-RETURNED-ERROR"