In article <3r81b3Fi346kU1@individual.net>,
S.Tobias <siXtY@FamOuS.BedBuG.pAlS.INVALID> wrote:
> This idea has been wandering around me for some time, too.
> It could work like this: programmer puts #pramas in the code,
> which contain verbatim quotes (or regexes, or identifires) of warnings
> that are to be suppressed for the next line. The utility program (or
> a script) calculates line numbers and produces a list of warnings
> (with the line numbers) to cut out from the compiler output.
> Like this:
> #pragma nowarn t.c:%n: warning: comparison between signed and unsigned
> if (u>s)
Lately, I've been fixing this with:
if (s < 0 || u > (unsigned) s)
but only after careful examination of what s really
represents. If s just contained a sloppy assignment from
what was previously an unsigned value, then no need for the
extra mathematical rigor.
Also, a lot these warnings arise from people using int when
they should have used size_t.
100% of our work is cutting-edge DSP
We are a small, high tech, sonar-processing company that develops state-of-the-art sonar, signal processing software systems used in naval aircraft.
* 60-75% signal processing algorithm development
* 25% real time code development in C++ Full relocation will be provided for the right candidate (e.g. relocation package up to $20,000).