From 239d71098048e4369f2cc1df6ff8c9483ae3a0a0 Mon Sep 17 00:00:00 2001 From: emarsden <emarsden> Date: Sun, 14 Sep 2003 19:11:18 +0000 Subject: [PATCH] Document a limitation of the XREF implementation: it does not delete stale information when recompiling a file. Will fix this limitation in the next few weeks. --- docs/cmu-user/cross-referencing.tex | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/cmu-user/cross-referencing.tex b/docs/cmu-user/cross-referencing.tex index a65dc3656..894555181 100644 --- a/docs/cmu-user/cross-referencing.tex +++ b/docs/cmu-user/cross-referencing.tex @@ -253,7 +253,11 @@ The cross-referencing database is not persistent: unless you save an image using \code{save-lisp}, the database will be empty each time \cmucl{} is restarted. There is no mechanism that saves cross-reference information in FASL files, so loading a system from -compiled code will not populate the cross-reference database. +compiled code will not populate the cross-reference database. The XREF +database currently accumulates ``stale'' information: when compiling a +file, it does not delete any cross-references that may have previously +been generated for that file. This latter limitation will be removed +in a future release. The cross-referencing facility is only able to analyze the static dependencies in a program; it does not provide any information about -- GitLab