From: David Carlton <carlton@kealia.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [obvious] Doc fix for cp-namespace.c
Date: Thu, 13 Nov 2003 19:35:00 -0000 [thread overview]
Message-ID: <yf2brrgvz89.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <vt2ekwcnpox.fsf@zenia.home> (Jim Blandy's message of "13 Nov 2003 12:28:14 -0500")
On 13 Nov 2003 12:28:14 -0500, Jim Blandy <jimb@redhat.com> said:
> 2003-11-13 Jim Blandy <jimb@redhat.com>
> * cp-namespace.c: Doc fix.
Thanks! You missed one, though, so I've commited the following patch.
David Carlton
carlton@kealia.com
2003-11-13 David Carlton <carlton@kealia.com>
* cp-namespace.c (lookup_namespace_scope): Fix typo in comment.
Index: cp-namespace.c
===================================================================
RCS file: /cvs/src/src/gdb/cp-namespace.c,v
retrieving revision 1.6
diff -u -p -r1.6 cp-namespace.c
--- cp-namespace.c 13 Nov 2003 17:28:37 -0000 1.6
+++ cp-namespace.c 13 Nov 2003 19:17:23 -0000
@@ -340,7 +340,7 @@ cp_lookup_symbol_nonlocal (const char *n
cp_lookup_symbol_nonlocal.
For example, if we're within a function A::B::f and looking for a
- symbol x, this will get called with NAME = "f", SCOPE = "A::B", and
+ symbol x, this will get called with NAME = "x", SCOPE = "A::B", and
SCOPE_LEN = 0. It then calls itself with NAME and SCOPE the same,
but with SCOPE_LEN = 1. And then it calls itself with NAME and
SCOPE the same, but with SCOPE_LEN = 4. This third call looks for
prev parent reply other threads:[~2003-11-13 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 17:30 Jim Blandy
2003-11-13 19:35 ` David Carlton [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=yf2brrgvz89.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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