From: Eric Blake <eblake@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: pbonzini@redhat.com, lcapitulino@redhat.com,
qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH V3 1/7] monitor: discard global variable *cur_mon in completion functions
Date: Fri, 28 Jun 2013 07:42:05 -0600 [thread overview]
Message-ID: <51CD92AD.3060805@redhat.com> (raw)
In-Reply-To: <51CCF436.1010904@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]
On 06/27/2013 08:25 PM, Wenchao Xia wrote:
>>> + readline_add_completion(mon->rs, file);
>>> }
>>> }
>>> closedir(ffs);
>>
>> Oops, I started reviewing that before noticing you posted a v3. At any
>> rate, my review of v2 still stands on this patch. Meanwhile, I just
>> barely noticed that this pre-existing code might cause a -Wshadow
>> warning in the future if <strings.h> is ever included. I'm not sure
>> what qemu's policy is on being clean against -Wshadow warnings, but I
>> personally tend to avoid local variables whose name might conflict with
>> global functions.
>>
> Thanks for reviewing. I'll fix what you mentioned in v2.
>
> For the -Wshadow warning, I guess you mean "file" right?
No, I meant ffs. ffs() is a global function, in scope if <strings.h> is
included; so using it as a local variable name will trigger -Wshadow
warnings from (at least some versions of) gcc.
> It would
> be a bit hard to check this warning for new patch, since this warning
> now exist in many code. In my opinion, it would be better to have a
> separate series to clean up this warnings first, then check new patches
> for this issue.
Agreed that the issue (of using ffs as a local variable name) is
pre-existing, and therefore cleanups for -Wshadow are not related to
this series and not something you need to necessarily worry about.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-06-28 13:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 3:27 [Qemu-devel] [PATCH V3 0/7] monitor: support sub command group in auto completion and help Wenchao Xia
2013-06-27 3:27 ` [Qemu-devel] [PATCH V3 1/7] monitor: discard global variable *cur_mon in completion functions Wenchao Xia
2013-06-27 21:26 ` Eric Blake
2013-06-28 2:25 ` Wenchao Xia
2013-06-28 13:42 ` Eric Blake [this message]
2013-06-27 3:27 ` [Qemu-devel] [PATCH V3 2/7] monitor: discard global variable *mon_cmds Wenchao Xia
2013-06-27 3:27 ` [Qemu-devel] [PATCH V3 3/7] monitor: discard global variable *info_cmds in help functions Wenchao Xia
2013-06-27 3:27 ` [Qemu-devel] [PATCH V3 4/7] monitor: code move for parse_cmdline() Wenchao Xia
2013-06-27 3:27 ` [Qemu-devel] [PATCH V3 5/7] monitor: support sub commands in auto completion Wenchao Xia
2013-06-27 3:27 ` [Qemu-devel] [PATCH V3 6/7] monitor: improve "help" in auto completion for sub command Wenchao Xia
2013-06-27 3:27 ` [Qemu-devel] [PATCH V3 7/7] monitor: improve "help" to allow show tip of single command in sub group Wenchao Xia
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=51CD92AD.3060805@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiawenc@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).