[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CLtL ambiguity in trace
- To: common-lisp@sail
- Subject: CLtL ambiguity in trace
- From: Steven Haflich <smh@mit-ems.ARPA>
- Date: Thu, 26 Sep 85 07:03:50 edt
The description on page 440:
trace {function-name}* [Macro]
Invoking trace with one or more function names (symbols)
causes the functions named to be traced. Henceforth,
whenever such a function is invoked ...
It is unclear whether the named function may legally be a macro.
This obviously-useful feature should not cause problems for any
implementation. It should be required, and the manual clarified.