On Friday 10 October 2003 16:42, Raymond Toy wrote:
> >>>>> "Peter" == Peter Denno <[EMAIL PROTECTED]> writes:
>
> Peter> Hi,
>
> Peter> I'd like to curtail the verbosity of cmucl output. One thing I
> tried was Peter> setting debug:*default-print-frame-call-verbosity* to 0.
> This variable is
>
> What kind of verbose output? The compiler output?
> print-frame-call-verbosity?
>
> Ray
Lot's of stuff really. It's all minor stuff, but it might be a bit of a shock
to someone just starting with cmucl. I'll demonstrate:
;;;============== EXAMPLE 1 - break on error ===============
Particularly I was referring to the stuff beginning below with "starting here
--->": (1) Printing the top of the stack seems redundant with the error
printed before the "Restarts:". And I can get that information easy. (2)
"Debug (type H for Help)" - isn't it enough that I have the debugger prompt?
(3) If I type "source" in the debugger I get the stuff beginning with
"Source:" Most times I don't want it. I noticed the variable
debug:*default-print-frame-call-verbosity* seemed involved with this output,
but changing it had no effect. I suppose it has to be set when cmucl is
compiled... or maybe I missed something there.
MA: (runit :teflon)
No matching method for the generic function
#<STANDARD-GENERIC-FUNCTION XML-QUERY-DATA-MODEL:CHILDREN (5) {28649939}>,
when
called with arguments (NIL).
[Condition of type PCL::NO-APPLICABLE-METHOD-ERROR]
Restarts:
0: [CONTINUE] Retry call to :FUNCTION.
1: [ABORT ] Return to Top-Level.
starting here ---------->
Debug (type H for help)
("DEFMETHOD NO-APPLICABLE-METHOD (T)" #<unused-arg> #<unused-arg>
#<STANDARD-GENERIC-FUNCTION XML-QUERY-DATA-MODEL:CHILDREN (5) {28649939}>
(NIL))
Source:
; File: target:pcl/braid.lisp
; File has been modified since compilation:
; target:pcl/braid.lisp
; Using form offset instead of character position.
(CERROR "Retry call to ~S."
'NO-APPLICABLE-METHOD-ERROR
:FUNCTION
GENERIC-FUNCTION
...)
<-------- ending here
MODELS|$
;;;============== EXAMPLE 2 -- compilation ======================
Since you brought up compiler output...
; Python version 1.1, VM version Intel x86 on 10 OCT 03 08:41:03 pm.
... That's not really useful. Maybe it could be said once at start-up.
; Compiling:
/home/pdenno/sis/repo/source/modelAnalysis/readers/xsd-reader.lisp 10 OCT 03
08:34:05 pm
... Putting the date and time here seems overkill.
; Compilation finished in 0:00:01.
... as does this. If I cared about time, I'd time it myself.
;;;============== EXAMPLE 3 -- compilation =========================
(1) Here I can (declaim (optimize (ext:inhibit-warnings 3))), but that isn't
sticky (I can't just put it in my init.lisp and be done with it). (2) We get
a similar warnings when evaluating an undeclared global at top level. I know
I can get rid of it, with (setf ext:*top-level-auto-declare* t), but I
wouldn't mind the message if it took up 1 line. However as it is, useful
stuff is scrolling off the screen.
; Loading #p"/opt/cl-binary/model-analysis/cmufasl/readers/xsd-reader.x86f".
;
;
; File: /home/pdenno/sis/repo/source/modelAnalysis/readers/xsd-reader.lisp
; In: DEFMETHOD |Element-Constructor| (XSD-CONSTRUCTION-CONTEXT T T T)
; (SETF *EEE* ELEM)
; ==>
; (SETQ *EEE* ELEM)
; Warning: Undefined variable *EEE*
; ;
; Warning: This variable is undefined:
; *EEE*
;
; Compilation unit finished.
; 2 warnings
... Why is that 2 warnings? It says the same thing twice for one line of code.
Then tells me there were two of them.
The above sounds like lots of whining. I don't mean to complain -- you guys
are doing a great job -- its just hard to find the relevant stuff in all this
output. I'd try to help, but just compiling cmucl is a pretty tough job. I
was successful at one time, but not lately
--
Best Regards,
- Peter
Peter Denno
National Institute of Standards and Technology,
Manufacturing System Integration Division,
100 Bureau Drive, Mail Stop 8264 Tel: +1 301-975-3595
Gaithersburg, MD, USA 20899-8264 FAX: +1 301-975-4694
