Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [patch 1/2] Perform a namespace lookup at every block level
Date: Tue, 10 Nov 2009 22:23:00 -0000	[thread overview]
Message-ID: <m3ljie9fzf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4ADE21F9.7020801@redhat.com> (Sami Wagiaalla's message of "Tue, 	20 Oct 2009 16:47:53 -0400")

>>>>> "Sami" == Sami Wagiaalla <swagiaal@redhat.com> writes:

Sami> I have added shadowing.exp to the patch which belongs to a future
Sami> patch but has some good tests, and it tests for the problem
Sami> pointed out by Daniel. I also added
Sami> namespace-multiple-imports.exp. Excuse the kfails; they will be
Sami> fixed by a future patch.

Thanks.

Sami> +static struct symbol *
Sami> +cp_lookup_symbol_in_namespace (const char *namespace,
Sami> +                   const char *name,
Sami> +                   const char *linkage_name,
Sami> +                   const struct block *block,
Sami> +                   const domain_enum domain)
Sami> +{
Sami> +

Extra blank line.

Sami> +static struct symbol *
Sami> +cp_lookup_symbol_imports (const char *scope,
Sami> +                          const char *name,
Sami> +                          const char *linkage_name,
Sami> +                          const struct block *block,
Sami> +                          const domain_enum domain)
[...]
Sami> +      /* If the import destination is the current scope or one of its ancestors then

Does this line go past column 80?  It looks like it.

Sami> +         it is applicable.  */
Sami> +      if (strncmp (scope, current->import_dest, strlen (current->import_dest)) == 0)

From my reading this doesn't exactly match the comment -- can
current->import_dest be an extension of scope?  Like, if scope is "x"
and import_dest is "xyz"?

Sami> diff --git a/gdb/testsuite/gdb.cp/namespace-using.exp b/gdb/testsuite/gdb.cp/namespace-using.exp
Sami> +    return -1;

No ";" here.

Otherwise this looks good.

Tom


  reply	other threads:[~2009-11-10 22:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10 15:10 [patch] " Sami Wagiaalla
2009-07-10 20:16 ` Daniel Jacobowitz
2009-07-13 17:55   ` Sami Wagiaalla
2009-07-23 19:46     ` Sami Wagiaalla
2009-07-23 22:19       ` Sami Wagiaalla
2009-07-29 22:12       ` Tom Tromey
2009-08-18 20:34       ` [patch 1/2] " Sami Wagiaalla
2009-10-13 19:47         ` Tom Tromey
2009-10-20 20:50           ` Sami Wagiaalla
2009-11-10 22:23             ` Tom Tromey [this message]
2009-11-10 22:26               ` Tom Tromey
2009-11-16 15:32                 ` Sami Wagiaalla
2009-11-16 19:16                   ` Sami Wagiaalla
2009-11-24 19:06                   ` Sami Wagiaalla
2009-12-21 21:44                     ` Tom Tromey
2009-08-18 20:46       ` [patch 2/2] " Sami Wagiaalla
2009-09-04 16:57         ` Sami Wagiaalla
2009-10-13 20:22           ` Tom Tromey
2009-10-22 17:47             ` Sami Wagiaalla
2009-11-10 22:52               ` Tom Tromey
2009-11-16 17:55                 ` Sami Wagiaalla
2009-11-24 19:12                   ` Sami Wagiaalla
2009-12-21 21:55                     ` Tom Tromey
2010-01-11 21:24                       ` Sami Wagiaalla
2010-01-12 17:43                         ` Tom Tromey
2010-01-14 16:47                           ` Sami Wagiaalla
2010-01-14 20:18                             ` Sami Wagiaalla
2010-01-15 18:06                               ` 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=m3ljie9fzf.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