From 5467c3a9cc22b004ca384107a926ea615282571d Mon Sep 17 00:00:00 2001 From: ram <ram> Date: Thu, 15 Feb 1990 12:02:55 +0000 Subject: [PATCH] Changed documentation for NODE-SOURCE-PATH to reflect the form-number being in the CAR of the list. --- compiler/node.lisp | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/compiler/node.lisp b/compiler/node.lisp index 5c1c63535..07d402bb7 100644 --- a/compiler/node.lisp +++ b/compiler/node.lisp @@ -184,12 +184,22 @@ ;; representation. (source nil :type t :read-only t) ;; - ;; List of integers describing the path taken through the source to get to - ;; this point. (k l m ...) => (nth k (nth l (nth m ...))) This path is - ;; through the original top-level form compiled, and in general has nothing - ;; to do with the Source slot. This path is our best guess for where the - ;; code came from, and may be not be very helpful in the case of code - ;; resulting from macroexpansion. + ;; A representation of the location in the original source of the form + ;; responsible for generating this node. The first element in this list is + ;; the "form number", which is the ordinal number of this form in a + ;; depth-first, left-to-right walk of the truly top-level form in which this + ;; appears. + ;; + ;; Following is a list of integers describing the path taken through the + ;; source to get to this point: + ;; (k l m ...) => (nth k (nth l (nth m ...))) + ;; + ;; This path is through the original top-level form compiled, and in general + ;; has nothing to do with the Source slot. This path is our best guess for + ;; where the code came from, and may be not be very helpful in the case of + ;; code resulting from macroexpansion. The last element in the list is the + ;; top-level form number, which is the ordinal number (in this call to the + ;; compiler) of the truly top-level form containing the orignal source (source-path *current-path* :type list :read-only t) ;; ;; If this node is in a tail-recursive position, then this is set to the -- GitLab