Git development
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Tomas Carnecky <tom@dbservice.com>, git list <git@vger.kernel.org>
Subject: Re: clang static analyzer
Date: Sun, 6 Dec 2009 11:04:36 -0500	[thread overview]
Message-ID: <20091206160436.GA7140@coredump.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0912061032380.31174@xanadu.home>

On Sun, Dec 06, 2009 at 10:39:56AM -0500, Nicolas Pitre wrote:

> >   2. If it is a false positive, see what it would take to silence clang
> >      and submit a patch.  I don't think we are opposed to annotations
> >      that help analysis tools as long as those annotations aren't too
> >      intrusive or make the code less readable.
> 
> I'm a bit skeptical here.  Going down that route might mean that we'll 
> eventually have to add all sort of crap to accommodate everyone's 
> preferred static analysis tool of the day.  Would be far nicer to try to 
> make those tools more intelligent instead, or at least make them 
> understand an out-of-line annotation format that does not clutter the 
> code itself.

To be clear, I am a bit skeptical, too. I would really prefer an
out-of-line annotation if one is available. But I am trying to encourage
the OP to actually make a patch for one instance so we can see just what
it would look like. Then we actually have a data point to discuss.

-Peff

  reply	other threads:[~2009-12-06 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06  6:11 clang static analyzer Tomas Carnecky
2009-12-06 14:57 ` Jeff King
2009-12-06 15:39   ` Nicolas Pitre
2009-12-06 16:04     ` Jeff King [this message]
2009-12-06 23:49       ` Nicolas Sebrecht
2009-12-07  0:18 ` Junio C Hamano
2009-12-07  0:26 ` Junio C Hamano

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=20091206160436.GA7140@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=tom@dbservice.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox