From: Michael J Gruber <git@drmicha.warpmail.net>
To: David Aguilar <davvid@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Thiago Farina <tfransosi@gmail.com>,
Andrew Wong <andrew.kw.w.lists@gmail.com>,
Andrew Wong <andrew.kw.w@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Scott Chacon <schacon@gmail.com>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Subject: Re: build deps
Date: Tue, 16 Oct 2012 09:37:41 +0200 [thread overview]
Message-ID: <507D0EC5.4030206@drmicha.warpmail.net> (raw)
In-Reply-To: <CAJDDKr5QaByGg0wW_fwFErRyMA6hbg2kHskxOqY4Z_rLoo1maQ@mail.gmail.com>
David Aguilar venit, vidit, dixit 16.10.2012 03:39:
> On Mon, Oct 15, 2012 at 1:53 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Michael J Gruber <git@drmicha.warpmail.net> writes:
>>
>>>> grep.c:451:16: warning: comparison of unsigned enum expression < 0 is
>>>> always false [-Wtautological-compare]
>>>> if (p->field < 0 || GREP_HEADER_FIELD_MAX <= p->field)
>>>> ~~~~~~~~ ^ ~
>>>> 1 warning generated.
>>>
>>> Right, that enum type starts at 0. Junio, you last touched this area.
>>> Can we just dump the first comparison or did you have something else in
>>> mind?
>>
>> I think it was a leftover from the very first implementation that
>> defensively said "this has to be one of these known ones", and tried
>> to bound it from both sides of the range, regaredless of the actual
>> type of the field (these GREP_HEADER_WHAT things may have been
>> simple integers with #define'd values). Dropping the "negative"
>> comparison is perfectly fine.
>
> This snippet of code came up before:
>
> http://thread.gmane.org/gmane.comp.version-control.git/184908/focus=185014
>
> There seemed to be good reasons to keep the check at the time.
>
> Was this same snippet not also touched when Nguyen Thai Ngoc Duy
> worked on the "even if I'm drunk" patch?:
>
> http://thread.gmane.org/gmane.comp.version-control.git/206413/focus=206539
>
> With the "drunk" patch then we wouldn't need the check at all,
> which is really nice.
>
> I hope that helps jog folks' memories.
> I'm not sure if the above discussions are relevant anymore,
> but I figured it'd be good to provide some more context.
>
> cheers,
The drunk patch, cheers ;)
That's very valuable context that you are giving. So it's either
avoiding the warning and relying and enum unsignedness (or human/static
analysis) or playing it safe and keeping the warning. How is
if (/* p->field < 0 || */ GREP_HEADER_FIELD_MAX <= p->field)
to remind any reader that the first condition should be granted? One
could take this further and use a macro but that seems overkill.
Michael
prev parent reply other threads:[~2012-10-16 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 0:39 build deps Thiago Farina
2012-10-08 16:09 ` Andrew Wong
2012-10-08 21:36 ` Thiago Farina
2012-10-08 21:37 ` Thiago Farina
2012-10-08 22:52 ` Andrew Wong
2012-10-11 20:54 ` Thiago Farina
2012-10-12 1:06 ` Andrew Wong
2012-10-12 4:08 ` Thiago Farina
2012-10-15 15:44 ` Michael J Gruber
2012-10-15 17:51 ` Thiago Farina
2012-10-15 20:53 ` Junio C Hamano
2012-10-16 1:39 ` David Aguilar
2012-10-16 7:37 ` Michael J Gruber [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=507D0EC5.4030206@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=andrew.kw.w.lists@gmail.com \
--cc=andrew.kw.w@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=schacon@gmail.com \
--cc=tfransosi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.