On 12/04/2012 16:35, Robert Dewar wrote:
> On 4/12/2012 10:48 AM, Andrew Haley wrote:
>
>> Ultimately, it's a matter of taste and experience. I'm going to find
>> it hard to write for people who don't know the relative precedence of
>> & and | .
>
> There are probably some programmers who completely know ALL the operator
> precedence rules in C. There are probably some subset of those who feel
> free to write code that takes full advantage of these rules. I would
> hate to read code written by such people :-)
I think it's worth suggesting, in the context of this discussion, that one
of the main purposes for which warnings exist in the first place is
*didactic*: they are very much intended to help teach the inexperienced about
the points of the language that they need to get straight in their heads, and
that their code /suggests/ that they haven't done so yet.
For that reason, I think that it's OK to have false-positive or slightly
over-sensitive warnings; certainly you don't want the noise to drown out the
signal, but unless they actually really do flood it out then they're not
necessarily a terribly bad thing in their own right.
cheers,
DaveK
