Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!sci.ccny.cuny.edu!phri!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: User introduced compiler warning, was Re: Behavior of #error
Keywords: #pragma warning
Message-ID: <14863@smoke.brl.mil>
Date: 15 Jan 91 21:52:24 GMT
References: <1192@van-bc.wimsey.bc.ca> <1991Jan15.102423.12793@watmath.waterloo.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 13

In article <1991Jan15.102423.12793@watmath.waterloo.edu> datangua@watmath.waterloo.edu (David Tanguay) writes:
>I've been using our compiler's #pragma warning "string" directive lately ...
>It's much less ignorable than
>	/* someday we should renooberate the frozbit */

There are some problems with this.  The main one is that it only works
for one particular compiler implementation, so you may have to go through
the code and fix these when porting to another platform.

We use /* XXX -- someday we should renooberate the frozbit */ comments
instead; this stands out pretty darn well when editing the code and it's
easy to grep for all XXX comments.  Also, it doesn't keep blathering
every time the code is compiled.