From: Tom Tromey <tromey@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] Renam sutruct using_direct members
Date: Thu, 04 Jun 2009 21:30:00 -0000 [thread overview]
Message-ID: <m3fxefwuv4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4A1AE557.6070300@redhat.com> (Sami Wagiaalla's message of "Mon\, 25 May 2009 14\:37\:11 -0400")
>>>>> "Sami" == Sami Wagiaalla <swagiaal@redhat.com> writes:
Sami> struct using_direct
Sami> {
Sami> char *inner;
Sami> char *outer;
Sami> struct using_direct *next;
Sami> };
Sami> The names inner and outer are not very clear. I certainly found it
Sami> unintuitive while working on namespace support. This patch renames them
Sami> no import_src and import_dest respectively
Seems reasonable. I agree that these names are not very clear.
Sami> 2009-05-25 Sami Wagiaalla <swagiaal@redhat.com>
Sami> * cp-support.h (struct using_direct): renamed members inner, and
Sami> outer to import_src, and import_dest respectively.
Sami> Updated all reverences.
A few nits about the ChangeLog... It should mention all files that
were changed. Descriptions should start with a capital letter. All
lines should start with a single TAB (the second one did not in the
email).
For this one I would write:
2009-05-25 Sami Wagiaalla <swagiaal@redhat.com>
* cp-support.h (struct using_direct): Rename members inner and
outer to import_src, and import_dest respectively.
* cp-namespace.c (cp_add_using_directive): Update.
(cp_add_using): Update.
(cp_copy_usings): Update.
(cp_lookup_symbol_namespace): Update.
* cp-support.c (make_symbol_overload_list_using): Update.
Also, your patch seems to have been wrapped at some places... wrong
MUA setting somewhere?
This is ok with an updated ChangeLog.
Tom
next prev parent reply other threads:[~2009-06-04 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 18:39 Sami Wagiaalla
2009-06-04 21:30 ` Tom Tromey [this message]
2009-06-30 16:44 ` Sami Wagiaalla
2009-06-30 21:25 ` Tom Tromey
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=m3fxefwuv4.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=swagiaal@redhat.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