Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] cleanup: Wunused corefile.c
Date: Fri, 01 Feb 2013 21:16:00 -0000	[thread overview]
Message-ID: <87boc34z0o.fsf@fleche.redhat.com> (raw)
In-Reply-To: <510AD43E.3040405@qnx.com> (Aleksandar Ristovski's message of	"Thu, 31 Jan 2013 15:29:50 -0500")

>>>>> "Aleksandar" == Aleksandar Ristovski <aristovski@qnx.com> writes:

Aleksandar> This is why I put a FIXME - intending to revisit and properly fix.

FIXME comments are just ignored in practice.  IME, nobody ever fixes
them except as a side effect of what they were intending to do.

Aleksandar> But there are other cases where it is not about missing code, but
Aleksandar> e.g. conditional compilation. For example:

Yeah, in that case I am less sure.
Making the definition conditional might be ok.
Or it might be uglier than the occasional ATTRIBUTE_UNUSED.
I guess it depends on the case.

Aleksandar> However, I do not intend to push this very hard due to lack
Aleksandar> of time. I simply did a swipe over the code and made it
Aleksandar> compile with Wunused (without regressions) on
Aleksandar> x86_64-linux-gnu and wanted to contribute as much as I can
Aleksandar> without spending too much time on it.

I understand, but I think the hard part of this work is also the most
useful part.  What I mean is that it is certainly valuable to get all
the simple cases fixed; but going through the trickier cases and writing
proper fixes is the real benefit of enabling this warning -- finding and
fixing real bugs.  Making these warnings disappear is contrary to that.

Tom


  reply	other threads:[~2013-02-01 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 19:36 Aleksandar Ristovski
2013-01-31 20:24 ` Tom Tromey
2013-01-31 20:29   ` Aleksandar Ristovski
2013-02-01 21:16     ` Tom Tromey [this message]
2013-02-01 21:31       ` Aleksandar Ristovski
2013-02-01 21:54         ` Aleksandar Ristovski
2013-02-03  0:05           ` Sergio Durigan Junior

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=87boc34z0o.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=aristovski@qnx.com \
    --cc=gdb-patches@sourceware.org \
    /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