Skip to content
Snippets Groups Projects
Commit 07d8f3eb authored by rtoy's avatar rtoy
Browse files

Document tracing for FLET/LABELS in the docstring.

parent c17bd546
No related branches found
No related tags found
No related merge requests found
......@@ -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
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment