From: Yao Qi <yao@codesourcery.com>
To: "Liu, Lei" <lei.liu2@windriver.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] call cp_lookup_symbol_namespace recursively to search symbols in C++ base classes
Date: Sun, 07 Nov 2010 10:04:00 -0000 [thread overview]
Message-ID: <4CD6798B.4030308@codesourcery.com> (raw)
In-Reply-To: <4CD27431.30401@windriver.com>
On 11/04/2010 04:52 PM, Liu, Lei wrote:
>
> I updated my patch to deal with this as long as the suggestions from
> Tom and Yao.
>
> I think in cp_set_block_scope, we should set scope name on a block
> regardless of whether processing_has_namespace_info has been set.
> For the cases that we only have classes but no namespaces, we still
> need scope information to tell us which symbols are valid in a block.
>
> How about this?
Lei,
It looks like your mail client eats spaces and tabs when you paste your
patch in your mail client. Please re-submit your patch again with
following steps,
1. Run 'git diff' to generate patch and dump it to a file, named
"foo.patch" for example,
2. Add your ChangeLog entry either in patch header or replied mail.
3. Reply mail in this thread, and *attach* your patch in your mail, and
send it out.
> + /* Just set the scope name if we get a valid one. */
Should be two spaces between "." and "*/". Please have a look at
"16.1.3 Comments" in
http://sourceware.org/gdb/current/onlinedocs/gdbint/Coding-Standards.html#Coding-Standards
--
Yao Qi
CodeSourcery
yao@codesourcery.com
(650) 331-3385 x739
next prev parent reply other threads:[~2010-11-07 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 3:47 Liu, Lei
2010-11-02 8:06 ` Yao Qi
2010-11-03 1:34 ` Liu, Lei
2010-11-02 20:31 ` Tom Tromey
2010-11-03 1:41 ` Liu, Lei
2010-11-03 0:10 ` Pedro Alves
2010-11-03 2:55 ` Liu, Lei
2010-11-03 17:57 ` Pedro Alves
2010-11-04 8:51 ` Liu, Lei
2010-11-07 10:04 ` Yao Qi [this message]
2010-11-08 1:38 ` Liu, Lei
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=4CD6798B.4030308@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=lei.liu2@windriver.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