[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue COMPILER-DIAGNOSTICS, version 7
- To: Jim McDonald <jlm@lucid.com>
- Subject: Re: issue COMPILER-DIAGNOSTICS, version 7
- From: David N Gray <Gray@DSG.csc.ti.com>
- Date: Mon, 19 Dec 88 12:04:17 CST
- Cc: sandra%defun@cs.utah.edu, cl-compiler@sail.stanford.edu
- In-reply-to: Msg of Fri, 16 Dec 88 15:46:12 PST from Jim McDonald <jlm@lucid.com>
- Sender: GRAY@Kelvin.csc.ti.com
> > Possibly NOTICE should write to *STANDARD-OUTPUT* rather than
> > *ERROR-OUTPUT*.
>
> Or to *TRACE-OUTPUT*, since notices are typically running commentary
> of import similar to "Entering FOO", "Leaving FOO", etc.
Yes, you would like such INFO conditions reported on the terminal, but I
would like ALERT conditions [e.g. "style warnings"] to be able to be
included in a DRIBBLE file. This makes me wonder if the concept of
combining these under the NOTICE condition might not be such a good idea.
It also reminds me of a point I raised a long time ago, that DRIBBLE ought
to bind *ERROR-OUTPUT* as well as *STANDARD-OUTPUT*. I still think it is
important that we not require compiler error messages to be written in
such a way that they can't be captured in a dribble file.