;; this punning with MAKE-LISP-OBJ depends for its safety on
;; the frame pointer being a lispobj-aligned integer. While
;; it is, then MAKE-LISP-OBJ will always return a FIXNUM, so
- ;; we're safe to do that. Should this ever change, than
+ ;; we're safe to do that. Should this ever change, this
;; MAKE-LISP-OBJ could return something that looks like a
;; pointer, but pointing into neverneverland, which will
- ;; confuse GC compiletely. -- CSR, 2003-06-03
+ ;; confuse GC completely. -- CSR, 2003-06-03
(get-mutex ,mutex (sb!kernel:make-lisp-obj (sb!sys:sap-int ,cfp))))
(unwind-protect
(progn ,@body)
(defun get-foreground ()
(when (not (eql (mutex-value *session-lock*) (current-thread-id)))
(get-mutex *session-lock*))
- (sb!sys:enable-interrupt :sigint #'sb!unix::sigint-handler)
+ (sb!sys:enable-interrupt sb!unix:sigint #'sb!unix::sigint-handler)
t)
#!-sb-thread
(defun get-foreground () t)
#!+sb-thread
(defun release-foreground ()
- (sb!sys:enable-interrupt :sigint :ignore)
+ (sb!sys:enable-interrupt sb!unix:sigint :ignore)
(release-mutex *session-lock*)
t)
#!-sb-thread