From 07d8f3eb1cf2b7bb0807c5a90fde2a52dc4e45b1 Mon Sep 17 00:00:00 2001
From: rtoy <rtoy>
Date: Tue, 20 Mar 2007 18:16:28 +0000
Subject: [PATCH] Document tracing for FLET/LABELS in the docstring.

---
 code/ntrace.lisp | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/code/ntrace.lisp b/code/ntrace.lisp
index 9707c3362..3eb3ae291 100644
--- a/code/ntrace.lisp
+++ b/code/ntrace.lisp
@@ -5,7 +5,7 @@
 ;;; Carnegie Mellon University, and has been placed in the public domain.
 ;;;
 (ext:file-comment
-  "$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/code/ntrace.lisp,v 1.36 2006/10/02 13:40:55 rtoy Exp $")
+  "$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/code/ntrace.lisp,v 1.37 2007/03/20 18:16:28 rtoy Exp $")
 ;;;
 ;;; **********************************************************************
 ;;;
@@ -672,6 +672,10 @@
    CLOS methods can be traced by specifying a name of the form
    (METHOD {Qualifier}* ({Specializer}*)).
 
+   Labels and Flet functions can be traced by specifying a name of the form
+   (LABELS <lfun> <fun>) or (FLET <lfun> <fun>) where <lfun> is the Labels/Flet
+   function in <fun>.
+
    TRACE causes a printout on *TRACE-OUTPUT* each time that one of the named
    functions is entered or returns (the Names are not evaluated.)  The output
    is indented according to the number of pending traced calls, and this trace
-- 
GitLab