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 2/2] namespace support
Date: Thu, 25 Jun 2009 15:59:00 -0000	[thread overview]
Message-ID: <m3bpocgv94.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4A428FA7.2040004@redhat.com> (Sami Wagiaalla's message of "Wed\, 24 Jun 2009 16\:42\:15 -0400")

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

Sami> I have added a test case.

Thanks.

Tom> I suppose these arguments ought to be renamed, now that you have
Tom> renamed the struct fields...

Sami> Agreed. Is it cool if I add this to the struct field rename patch.

Sure, just remember to post the updated patch.

Sami> +	      int outer_len = (previous_component == 0 ? 0 : previous_component - 2);
Sami> +	      int inner_len = next_component;
Sami> +	      char *outer = alloca (outer_len + 1);
Sami> +	      char *inner = alloca (inner_len + 1);
Sami> +
Sami> +	      strncpy(outer, name, outer_len);
Sami> +	      strncpy(inner, name, inner_len);

Missing spaces before the open parens.
Also, I think you should just use memcpy here.

Sami> +int main(){
Sami> +  using namespace A::B;
Sami> +  return C::x;
Sami> +}
Sami> \ No newline at end of file

Add a newline...

Sami> +gdb_test "print C::x" "= 5"
Sami> \ No newline at end of file

... and here too.

Ok with those changes.  Thanks.

Tom


      reply	other threads:[~2009-06-25 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 14:52 Sami Wagiaalla
2009-06-05 21:20 ` Tom Tromey
2009-06-24 20:43   ` Sami Wagiaalla
2009-06-25 15:59     ` Tom Tromey [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=m3bpocgv94.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