From: Pedro Alves <pedro@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 034/238] [misc.] Fix -Wshadow warnings.
Date: Tue, 06 Dec 2011 18:25:00 -0000 [thread overview]
Message-ID: <201112061759.39946.pedro@codesourcery.com> (raw)
In-Reply-To: <20111205132646.GA3430@adacore.com>
On Monday 05 December 2011 13:26:46, Joel Brobecker wrote:
> > > Looks OK to me. But Pedro might comment on the new variable name
> > > (sal->sal2).
> [...]
> > Initially it was sal->las which probably isn't better, so I'll wait
> > for some consensus to arise on this patch too.
>
> FWIW, I'm OK with sal2. I also agree with stan that it's best to
> avoid `las' (cute, though :-))
sal2 is fine with me too.
There might actually be a bug here, that I still haven't managed
to investigate:
http://sourceware.org/ml/gdb-patches/2011-03/msg00066.html
(but don't let this block your patch.)
Michael wanted sal2 too, so sal2 it is.
Curiously, we have very few instances of struct symtab_and_line
that aren't called "sal" or don't have "sal" in their name:
$ grep "struct symtab_and_line[ \t]\+[A-Za-z_]\+;" * -rn | grep -v sal
linespec.c:1910: struct symtab_and_line val;
linespec.c:2000: struct symtab_and_line val;
mi/mi-cmd-file.c:36: struct symtab_and_line st;
symtab.c:1923: struct symtab_and_line val;
But they're all close enough. Interestingly, sal2 is the first. :-)
$ grep sal2 * -rn
*empty*
Sals are funny creatures.
--
Pedro Alves
prev parent reply other threads:[~2011-12-06 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 13:25 [PATCH 35/358] Fix -Wsahdow warnings Andrey Smirnov
2011-11-22 19:19 ` Tom Tromey
2011-11-23 0:35 ` Stan Shebs
2011-11-23 4:46 ` Andrey Smirnov
2011-11-28 15:19 ` [PATCH 034/238] [misc.] Fix -Wshadow warnings Andrey Smirnov
2011-12-05 11:30 ` Joel Brobecker
2011-12-05 13:27 ` Andrey Smirnov
2011-12-05 13:31 ` Joel Brobecker
2011-12-06 18:25 ` Pedro Alves [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=201112061759.39946.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=andrew.smirnov@gmail.com \
--cc=brobecker@adacore.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