[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
issue DEFINING-MACROS-NON-TOP-LEVEL (Version 4)
- To: KMP@STONY-BROOK.SCRC.Symbolics.COM
- Subject: issue DEFINING-MACROS-NON-TOP-LEVEL (Version 4)
- From: Jim McDonald <firstname.lastname@example.org>
- Date: Tue, 27 Sep 88 16:29:22 PDT
- Cc: Gray@DSG.csc.ti.com, KMP@STONY-BROOK.SCRC.Symbolics.COM, email@example.com, CL-Compiler@SAIL.Stanford.edu
- In-reply-to: Kent M Pitman's message of Tue, 27 Sep 88 12:34 EDT <880927123446.1.KMP@GRYPHON.SCRC.Symbolics.COM>
Nothing bugs me more than warnings about valid code. ...
I can't see the -real- warnings the compiler might have issued through
all the gratuitous ones. ...
From time to time (daily?) I've wanted a function I mentally call
NOTE, which is similar to WARN but separately controllable, to be used
for presenting benign commentary. Then observations about cultural
conventions, dead code, useless declarations, failed optimizations,
etc. could all be shunted to a separate stream from those about
variables being free, symbols used previously as functions being
defined as macros, etc.
I could also then ask for *break-on-warnings* separately from
*break-on-notes*, and not have to endure 20 spurious breaks to
get to the real problems...