;;;; Environment query functions, DOCUMENTATION and DRIBBLE. ;;;; ;;;; FIXME: If there are exactly three things in here, it could be ;;;; exactly three files named e.g. equery.lisp, doc.lisp, and dribble.lisp. ;;;; This software is part of the SBCL system. See the README file for ;;;; more information. ;;;; ;;;; This software is derived from the CMU CL system, which was ;;;; written at Carnegie Mellon University and released into the ;;;; public domain. The software is in the public domain and is ;;;; provided with absolutely no warranty. See the COPYING and CREDITS ;;;; files for more information. (in-package "SB!IMPL") ;;;; function names and documentation ;;;; the ANSI interface to function names (and to other stuff too) (defun function-lambda-expression (fun) "Return (VALUES DEFINING-LAMBDA-EXPRESSION CLOSURE-P NAME), where DEFINING-LAMBDA-EXPRESSION is NIL if unknown, or a suitable argument to COMPILE otherwise, CLOSURE-P is non-NIL if the function's definition might have been enclosed in some non-null lexical environment, and NAME is some name (for debugging only) or NIL if there is no name." (declare (type function fun)) (let* ((fun (%simple-fun-self fun)) (name (%fun-name fun)) (code (sb!di::fun-code-header fun)) (info (sb!kernel:%code-debug-info code))) (if info (let ((source (first (sb!c::compiled-debug-info-source info)))) (cond ((and (eq (sb!c::debug-source-from source) :lisp) (eq (sb!c::debug-source-info source) fun)) (values (svref (sb!c::debug-source-name source) 0) nil name)) ;; FIXME: shouldn't these two clauses be the other way ;; round? Using VALID-FUNCTION-NAME-P to see if we ;; want to find an inline-expansion? ((stringp name) (values nil t name)) (t (let ((exp (fun-name-inline-expansion name))) (if exp (values exp nil name) (values nil t name)))))) (values nil t name)))) ;;; a SETFable function to return the associated debug name for FUN ;;; (i.e., the third value returned from CL:FUNCTION-LAMBDA-EXPRESSION), ;;; or NIL if there's none (defun %fun-name (fun) (case (widetag-of fun) (#.sb!vm:closure-header-widetag (%simple-fun-name (%closure-fun fun))) ((#.sb!vm:simple-fun-header-widetag #.sb!vm:closure-fun-header-widetag) ;; KLUDGE: The pun that %SIMPLE-FUN-NAME is used for closure ;; functions is left over from CMU CL (modulo various renaming ;; that's gone on since the fork). (%simple-fun-name fun)) (#.sb!vm:funcallable-instance-header-widetag (%simple-fun-name (funcallable-instance-fun fun))))) (defun (setf %fun-name) (new-name fun) (aver nil) ; since this is unsafe 'til bug 137 is fixed (let ((widetag (widetag-of fun))) (case widetag ((#.sb!vm:simple-fun-header-widetag #.sb!vm:closure-fun-header-widetag) ;; KLUDGE: The pun that %SIMPLE-FUN-NAME is used for closure ;; functions is left over from CMU CL (modulo various renaming ;; that's gone on since the fork). (setf (%simple-fun-name fun) new-name)) (#.sb!vm:closure-header-widetag ;; FIXME: It'd be nice to be able to set %FUN-NAME here on ;; per-closure basis. Instead, we are still using the CMU CL ;; approach of closures being named after their closure ;; function, which doesn't work right e.g. for structure ;; accessors, and might not be quite right for DEFUN ;; in a non-null lexical environment either. ;; When/if weak hash tables become supported ;; again, it'll become easy to fix this, but for now there ;; seems to be no easy way (short of the ugly way of adding a ;; slot to every single closure header), so we don't. ;; ;; Meanwhile, users might encounter this problem by doing DEFUN ;; in a non-null lexical environment, so we try to give a ;; reasonably meaningful user-level "error" message (but only ;; as a warning because this is optional debugging ;; functionality anyway, not some hard ANSI requirement). (warn "can't set name for closure, leaving name unchanged")) (t ;; The other function subtype names are also un-settable ;; but this problem seems less likely to be tickled by ;; user-level code, so we can give a implementor-level ;; "error" (warning) message. (warn "can't set function name ((~S function)=~S), leaving it unchanged" 'widetag-of widetag)))) new-name) (defun %fun-doc (x) ;; FIXME: This business of going through %FUN-NAME and then globaldb ;; is the way CMU CL did it, but it doesn't really seem right. ;; When/if weak hash tables become supported again, using a weak ;; hash table to maintain the object/documentation association would ;; probably be better. (let ((name (%fun-name x))) (when (and name (typep name '(or symbol cons))) (values (info :function :documentation name))))) ;;; various environment inquiries (defvar *features* '#.sb-cold:*shebang-features* #!+sb-doc "a list of symbols that describe features provided by the implementation") (defun machine-instance () #!+sb-doc "Return a string giving the name of the local machine." (sb!unix:unix-gethostname)) ;;; FIXME: Don't forget to set these in a sample site-init file. ;;; FIXME: Perhaps the functions could be SETFable instead of having the ;;; interface be through special variables? As far as I can tell ;;; from ANSI 11.1.2.1.1 "Constraints on the COMMON-LISP Package ;;; for Conforming Implementations" it is kosher to add a SETF function for ;;; a symbol in COMMON-LISP.. (defvar *short-site-name* nil #!+sb-doc "The value of SHORT-SITE-NAME.") (defvar *long-site-name* nil #!+sb-doc "the value of LONG-SITE-NAME") (defun short-site-name () #!+sb-doc "Return a string with the abbreviated site name, or NIL if not known." *short-site-name*) (defun long-site-name () #!+sb-doc "Return a string with the long form of the site name, or NIL if not known." *long-site-name*) ;;;; dribble stuff ;;; Each time we start dribbling to a new stream, we put it in ;;; *DRIBBLE-STREAM*, and push a list of *DRIBBLE-STREAM*, *STANDARD-INPUT*, ;;; *STANDARD-OUTPUT* and *ERROR-OUTPUT* in *PREVIOUS-DRIBBLE-STREAMS*. ;;; *STANDARD-OUTPUT* and *ERROR-OUTPUT* is changed to a broadcast stream that ;;; broadcasts to *DRIBBLE-STREAM* and to the old values of the variables. ;;; *STANDARD-INPUT* is changed to an echo stream that echos input from the old ;;; value of standard input to *DRIBBLE-STREAM*. ;;; ;;; When dribble is called with no arguments, *DRIBBLE-STREAM* is closed, ;;; and the values of *DRIBBLE-STREAM*, *STANDARD-INPUT*, and ;;; *STANDARD-OUTPUT* are popped from *PREVIOUS-DRIBBLE-STREAMS*. (defvar *previous-dribble-streams* nil) (defvar *dribble-stream* nil) (defun dribble (&optional pathname &key (if-exists :append)) #!+sb-doc "With a file name as an argument, dribble opens the file and sends a record of further I/O to that file. Without an argument, it closes the dribble file, and quits logging." (cond (pathname (let* ((new-dribble-stream (open pathname :direction :output :if-exists if-exists :if-does-not-exist :create)) (new-standard-output (make-broadcast-stream *standard-output* new-dribble-stream)) (new-error-output (make-broadcast-stream *error-output* new-dribble-stream)) (new-standard-input (make-echo-stream *standard-input* new-dribble-stream))) (push (list *dribble-stream* *standard-input* *standard-output* *error-output*) *previous-dribble-streams*) (setf *dribble-stream* new-dribble-stream) (setf *standard-input* new-standard-input) (setf *standard-output* new-standard-output) (setf *error-output* new-error-output))) ((null *dribble-stream*) (error "not currently dribbling")) (t (let ((old-streams (pop *previous-dribble-streams*))) (close *dribble-stream*) (setf *dribble-stream* (first old-streams)) (setf *standard-input* (second old-streams)) (setf *standard-output* (third old-streams)) (setf *error-output* (fourth old-streams))))) (values)) (defun %byte-blt (src src-start dst dst-start dst-end) (%byte-blt src src-start dst dst-start dst-end))