1 ;;;; various user-level definitions which need to be done particularly
4 ;;;; This software is part of the SBCL system. See the README file for
7 ;;;; This software is derived from the CMU CL system, which was
8 ;;;; written at Carnegie Mellon University and released into the
9 ;;;; public domain. The software is in the public domain and is
10 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
11 ;;;; files for more information.
13 (in-package "SB!IMPL")
15 ;;;; target constants which need to appear as early as possible
17 ;;; an internal tag for marking empty slots, which needs to be defined
18 ;;; as early as possible because it appears in macroexpansions for
19 ;;; iteration over hash tables
21 ;;; CMU CL 18b used :EMPTY for this purpose, which was somewhat nasty
22 ;;; since it's easily accessible to the user, so that e.g.
23 ;;; (DEFVAR *HT* (MAKE-HASH-TABLE))
24 ;;; (SETF (GETHASH :EMPTY *HT*) :EMPTY)
25 ;;; (MAPHASH (LAMBDA (K V) (FORMAT T "~&~S ~S~%" K V)))
26 ;;; gives no output -- oops!
28 ;;; FIXME: It'd probably be good to use the unbound marker for this.
29 ;;; However, there might be some gotchas involving assumptions by
30 ;;; e.g. AREF that they're not going to return the unbound marker,
31 ;;; and there's also the noted-below problem that the C-level code
32 ;;; contains implicit assumptions about this marker.
34 ;;; KLUDGE: Note that as of version 0.pre7 there's a dependence in the
35 ;;; gencgc.c code on this value being a symbol. (This is only one of
36 ;;; several nasty dependencies between that code and this, alas.)
38 (eval-when (:compile-toplevel :load-toplevel :execute)
39 (def!constant +empty-ht-slot+ '%empty-ht-slot%))
40 ;;; We shouldn't need this mess now that EVAL-WHEN works.
42 ;;; KLUDGE: Using a private symbol still leaves us vulnerable to users
43 ;;; getting nonconforming behavior by messing around with
44 ;;; DO-ALL-SYMBOLS. That seems like a fairly obscure problem, so for
45 ;;; now we just don't worry about it. If for some reason it becomes
46 ;;; worrisome and the magic value needs replacement:
47 ;;; * The replacement value needs to be LOADable with EQL preserved,
48 ;;; so that the macroexpansion for WITH-HASH-TABLE-ITERATOR will
49 ;;; work when compiled into a file and loaded back into SBCL.
50 ;;; (Thus, just uninterning %EMPTY-HT-SLOT% doesn't work.)
51 ;;; * The replacement value needs to be acceptable to the
52 ;;; low-level gencgc.lisp hash table scavenging code.
53 ;;; * The change will break binary compatibility, since comparisons
54 ;;; against the value used at the time of compilation are wired
58 ;;;; DO-related stuff which needs to be visible on the cross-compilation host
60 (eval-when (#-sb-xc :compile-toplevel :load-toplevel :execute)
61 (defun frob-do-body (varlist endlist decls-and-code bind step name block)
62 (let* ((r-inits nil) ; accumulator for reversed list
63 (r-steps nil) ; accumulator for reversed list
66 ;; Check for illegal old-style DO.
67 (when (or (not (listp varlist)) (atom endlist))
68 (error "ill-formed ~S -- possibly illegal old style DO?" name))
69 ;; Parse VARLIST to get R-INITS and R-STEPS.
71 (flet (;; (We avoid using CL:PUSH here so that CL:PUSH can be
72 ;; defined in terms of CL:SETF, and CL:SETF can be
73 ;; defined in terms of CL:DO, and CL:DO can be defined
74 ;; in terms of the current function.)
76 (setq r-inits (cons x r-inits)))
77 ;; common error-handling
79 (error "~S is an illegal form for a ~S varlist." v name)))
80 (cond ((symbolp v) (push-on-r-inits v))
82 (unless (symbolp (first v))
83 (error "~S step variable is not a symbol: ~S"
86 (let ((lv (length v)))
87 ;; (We avoid using CL:CASE here so that CL:CASE can
88 ;; be defined in terms of CL:SETF, and CL:SETF can
89 ;; be defined in terms of CL:DO, and CL:DO can be
90 ;; defined in terms of the current function.)
92 (push-on-r-inits (first v)))
96 (push-on-r-inits (list (first v) (second v)))
97 (setq r-steps (list* (third v) (first v) r-steps)))
98 (t (illegal-varlist)))))
99 (t (illegal-varlist)))))
100 ;; Construct the new form.
101 (multiple-value-bind (code decls) (parse-body decls-and-code nil)
103 (,bind ,(nreverse r-inits)
109 (,step ,@(nreverse r-steps))
111 (unless ,(first endlist) (go ,label-1))
112 (return-from ,block (progn ,@(rest endlist))))))))))
114 ;;; This is like DO, except it has no implicit NIL block. Each VAR is
115 ;;; initialized in parallel to the value of the specified INIT form.
116 ;;; On subsequent iterations, the VARS are assigned the value of the
117 ;;; STEP form (if any) in parallel. The TEST is evaluated before each
118 ;;; evaluation of the body FORMS. When the TEST is true, the
119 ;;; EXIT-FORMS are evaluated as a PROGN, with the result being the
121 (defmacro do-anonymous (varlist endlist &rest body)
122 (frob-do-body varlist endlist body 'let 'psetq 'do-anonymous (gensym)))
126 ;;; Automate an idiom often found in macros:
127 ;;; (LET ((FOO (GENSYM "FOO"))
128 ;;; (MAX-INDEX (GENSYM "MAX-INDEX-")))
131 ;;; "Good notation eliminates thought." -- Eric Siggia
133 ;;; Incidentally, this is essentially the same operator which
134 ;;; _On Lisp_ calls WITH-GENSYMS.
135 (defmacro with-unique-names (symbols &body body)
136 `(let ,(mapcar (lambda (symbol)
137 (let* ((symbol-name (symbol-name symbol))
138 (stem (if (every #'alpha-char-p symbol-name)
140 (concatenate 'string symbol-name "-"))))
141 `(,symbol (gensym ,stem))))
145 ;;; Return a list of N gensyms. (This is a common suboperation in
146 ;;; macros and other code-manipulating code.)
147 (declaim (ftype (function (index) list) make-gensym-list))
148 (defun make-gensym-list (n)
149 (loop repeat n collect (gensym)))
153 ;;; Lots of code wants to get to the KEYWORD package or the
154 ;;; COMMON-LISP package without a lot of fuss, so we cache them in
155 ;;; variables. TO DO: How much does this actually buy us? It sounds
156 ;;; sensible, but I don't know for sure that it saves space or time..
159 ;;; (The initialization forms here only matter on the cross-compilation
160 ;;; host; In the target SBCL, these variables are set in cold init.)
161 (declaim (type package *cl-package* *keyword-package*))
162 (defvar *cl-package* (find-package "COMMON-LISP"))
163 (defvar *keyword-package* (find-package "KEYWORD"))
165 ;;; Concatenate together the names of some strings and symbols,
166 ;;; producing a symbol in the current package.
167 (eval-when (#-sb-xc :compile-toplevel :load-toplevel :execute)
168 (defun symbolicate (&rest things)
169 (let ((name (case (length things)
170 ;; why isn't this just the value in the T branch?
171 ;; Well, this is called early in cold-init, before
172 ;; the type system is set up; however, now that we
173 ;; check for bad lengths, the type system is needed
174 ;; for calls to CONCATENATE. So we need to make sure
175 ;; that the calls are transformed away:
176 (1 (concatenate 'string
177 (the simple-base-string (string (car things)))))
178 (2 (concatenate 'string
179 (the simple-base-string (string (car things)))
180 (the simple-base-string (string (cadr things)))))
181 (3 (concatenate 'string
182 (the simple-base-string (string (car things)))
183 (the simple-base-string (string (cadr things)))
184 (the simple-base-string (string (caddr things)))))
185 (t (apply #'concatenate 'string (mapcar #'string things))))))
186 (values (intern name)))))
188 ;;; like SYMBOLICATE, but producing keywords
189 (defun keywordicate (&rest things)
190 (let ((*package* *keyword-package*))
191 (apply #'symbolicate things)))
193 ;;; Access *PACKAGE* in a way which lets us recover when someone has
194 ;;; done something silly like (SETF *PACKAGE* :CL-USER). (Such an
195 ;;; assignment is undefined behavior, so it's sort of reasonable for
196 ;;; it to cause the system to go totally insane afterwards, but it's a
197 ;;; fairly easy mistake to make, so let's try to recover gracefully
199 (defun sane-package ()
200 (let ((maybe-package *package*))
201 (cond ((and (packagep maybe-package)
202 ;; For good measure, we also catch the problem of
203 ;; *PACKAGE* being bound to a deleted package.
204 ;; Technically, this is not undefined behavior in itself,
205 ;; but it will immediately lead to undefined to behavior,
206 ;; since almost any operation on a deleted package is
208 (package-name maybe-package))
211 ;; We're in the undefined behavior zone. First, munge the
212 ;; system back into a defined state.
213 (let ((really-package (find-package :cl-user)))
214 (setf *package* really-package)
216 (error 'simple-type-error
218 :expected-type '(and package (satisfies package-name))
220 "~@<~S can't be a ~A: ~2I~_~S has been reset to ~S.~:>"
221 :format-arguments (list '*package*
222 (if (packagep maybe-package)
224 (type-of maybe-package))
225 '*package* really-package)))))))
227 ;;; Access *DEFAULT-PATHNAME-DEFAULTS*, issuing a warning if its value
228 ;;; is silly. (Unlike the vaguely-analogous SANE-PACKAGE, we don't
229 ;;; actually need to reset the variable when it's silly, since even
230 ;;; crazy values of *DEFAULT-PATHNAME-DEFAULTS* don't leave the system
231 ;;; in a state where it's hard to recover interactively.)
232 (defun sane-default-pathname-defaults ()
233 (let* ((dfd *default-pathname-defaults*)
234 (dfd-dir (pathname-directory dfd)))
235 ;; It's generally not good to use a relative pathname for
236 ;; *DEFAULT-PATHNAME-DEFAULTS*, since relative pathnames
237 ;; are defined by merging into a default pathname (which is,
238 ;; by default, *DEFAULT-PATHNAME-DEFAULTS*).
239 (when (and (consp dfd-dir)
240 (eql (first dfd-dir) :relative))
242 "~@<~S is a relative pathname. (But we'll try using it anyway.)~@:>"
243 '*default-pathname-defaults*))
246 ;;; Give names to elements of a numeric sequence.
247 (defmacro defenum ((&key (prefix "") (suffix "") (start 0) (step 1))
253 (dolist (id identifiers)
255 (multiple-value-bind (root docs)
257 (values (car id) (cdr id))
259 (push `(def!constant ,(symbolicate prefix root suffix)
260 ,(+ start (* step index))
265 ,@(nreverse results))))
267 ;;; generalization of DEFCONSTANT to values which are the same not
268 ;;; under EQL but under e.g. EQUAL or EQUALP
270 ;;; DEFCONSTANT-EQX is to be used instead of DEFCONSTANT for values
271 ;;; which are appropriately compared using the function given by the
272 ;;; EQX argument instead of EQL.
274 ;;; Note: Be careful when using this macro, since it's easy to
275 ;;; unintentionally pessimize your code. A good time to use this macro
276 ;;; is when the values defined will be fed into optimization
277 ;;; transforms and never actually appear in the generated code; this
278 ;;; is especially common when defining BYTE expressions. Unintentional
279 ;;; pessimization can result when the values defined by this macro are
280 ;;; actually used in generated code: because of the way that the
281 ;;; dump/load system works, you'll typically get one copy of consed
282 ;;; structure for each object file which contains code referring to
283 ;;; the value, plus perhaps one more copy bound to the SYMBOL-VALUE of
284 ;;; the constant. If you don't want that to happen, you should
285 ;;; probably use DEFPARAMETER instead; or if you truly desperately
286 ;;; need to avoid runtime indirection through a symbol, you might be
287 ;;; able to do something with LOAD-TIME-VALUE or MAKE-LOAD-FORM.
288 (defmacro defconstant-eqx (symbol expr eqx &optional doc)
289 `(def!constant ,symbol
290 (%defconstant-eqx-value ',symbol ,expr ,eqx)
291 ,@(when doc (list doc))))
292 (defun %defconstant-eqx-value (symbol expr eqx)
293 (declare (type function eqx))
294 (flet ((bummer (explanation)
295 (error "~@<bad DEFCONSTANT-EQX ~S ~2I~_~S: ~2I~_~A ~S~:>"
299 (symbol-value symbol))))
300 (cond ((not (boundp symbol))
302 ((not (constantp symbol))
303 (bummer "already bound as a non-constant"))
304 ((not (funcall eqx (symbol-value symbol) expr))
305 (bummer "already bound as a different constant value"))
307 (symbol-value symbol)))))
309 ;;; a helper function for various macros which expect clauses of a
310 ;;; given length, etc.
312 ;;; Return true if X is a proper list whose length is between MIN and
314 (defun proper-list-of-length-p (x min &optional (max min))
315 ;; FIXME: This implementation will hang on circular list
316 ;; structure. Since this is an error-checking utility, i.e. its
317 ;; job is to deal with screwed-up input, it'd be good style to fix
318 ;; it so that it can deal with circular list structure.
319 (cond ((minusp max) nil)
320 ((null x) (zerop min))
323 (proper-list-of-length-p (cdr x)