From: Joel Brobecker <brobecker@adacore.com>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 18/348] Fix -Wsahdow warnings
Date: Thu, 24 Nov 2011 22:01:00 -0000 [thread overview]
Message-ID: <20111124220057.GU13809@adacore.com> (raw)
In-Reply-To: <CAHQ1cqHjSYQL75PS8xqEASXXnh5jzMGH+JX7ti_9SKZ+5UOtKA@mail.gmail.com>
Andrey,
I understand your fustration towards the tone of some of the messages.
Hopefully things will be better from now on.
And I agree that not enabling -Wshadow by default will let the number
of such conflict increase again over time. But at the same time, now
that I am seeing the changes that are required to fix these, I am not
very happy either. I mean, I understand that "index" might be part of
a system's include. But "block_found" (or was it "found_block") seems
quite surprising. Add the fact that includes and compiler vary from
system to system, and we're not sure that once clean on one machine,
it'll be clean everywhere else. All of this to fix warnings that,
as far as I could tell for the most part, did not indicate an actual
bug in the code.
This is why I am left wondering (meaning I haven't decided yet)
whether the idea of enabling -Wshadow was such a good idea after
all. I know that looking at the warnings allowed you to spot some
areas where there definitely is a mistake, and so that's useful.
I'm not disputing that. But I'm not convinced by a good number of
the patches I've seen, and I still haven't decided whether to
accept the situation and approve them, or not. For that, I asked
everyone else' opinion.
--
Joel
next prev parent reply other threads:[~2011-11-24 22:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 13:01 Andrey Smirnov
2011-11-22 18:03 ` Tom Tromey
2011-11-23 16:36 ` Mark Kettenis
2011-11-23 16:41 ` Ulrich Weigand
2011-11-23 18:21 ` Pedro Alves
2011-11-23 18:42 ` Joel Brobecker
2011-11-23 20:24 ` Mark Kettenis
2011-11-24 4:16 ` Andrey Smirnov
2011-11-24 11:36 ` Eli Zaretskii
2011-11-24 22:01 ` Joel Brobecker [this message]
2011-11-25 0:48 ` Andrey Smirnov
2011-11-25 14:26 ` Joel Brobecker
2011-11-25 15:52 ` About adding -Wshadow option by default (was Re: [PATCH 18/348] Fix -Wsahdow warnings) Pierre Muller
2011-11-25 16:36 ` Mark Kettenis
2011-11-29 19:18 ` [PATCH 18/348] Fix -Wsahdow warnings Tom Tromey
2011-11-30 3:48 ` Andrey Smirnov
2011-11-30 14:59 ` Tom Tromey
2011-12-01 4:15 ` Andrey Smirnov
2011-12-02 17:08 ` Tom Tromey
2011-11-25 12:03 ` Eli Zaretskii
2011-11-25 15:11 ` Mark Kettenis
2011-11-25 15:41 ` Eli Zaretskii
2011-11-25 16:26 ` Mark Kettenis
2011-11-25 18:20 ` Eli Zaretskii
2011-11-27 13:53 ` Mark Kettenis
2011-11-27 14:55 ` Pedro Alves
2011-11-27 16:35 ` Eli Zaretskii
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=20111124220057.GU13809@adacore.com \
--to=brobecker@adacore.com \
--cc=andrew.smirnov@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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