[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
issue COMPILER-DIAGNOSTICS, version 7
- To: sandra%defun@cs.utah.edu
- Subject: issue COMPILER-DIAGNOSTICS, version 7
- From: Jim McDonald <jlm@lucid.com>
- Date: Fri, 30 Dec 88 19:37:25 PST
- Cc: KMP@STONY-BROOK.SCRC.Symbolics.COM, sandra%defun@cs.utah.edu, cl-compiler@sail.stanford.edu
- In-reply-to: Sandra J Loosemore's message of Fri, 30 Dec 88 12:30:13 MST <8812301930.AA03628@defun.utah.edu>
> it won't do anything to solve the stated problem, namely how to
> suppress useless style warning messages.
In the original message I sent which (I think) spurred Pierson's
proposal, I had in mind a related class of messages generated by users
(not the compiler per se), which should be captured by the same
mechanism, e.g.:
;;; NOTE: Compiling file foo.lisp (234 out of 567) at 12:54 30-Dec-88
;;; NOTE: This uses the NEW (11-Nov-88) version of magic-macro.
I envisoned a form like NOTE, analogous to WARN, but the real goals
were just (1) to be able to suppress all such messages without
suppressing any significant warning messages and (2) to be able to
break on such messages, analogous to *break-on-warnings*, since they
often represent good debugging points in the main flow of control.
A user can always craft their own such mechanism, but if they can
piggy-back on an existing mechanism their world is just a bit simpler.
This requires some sort of user-accessible function, condition, etc.,
which Pierson's proposal would provide.
jlm