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] support argument dependent lookup (ADL)
Date: Fri, 23 Apr 2010 22:34:00 -0000	[thread overview]
Message-ID: <m3iq7hx0fu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1270829129.2387.23.camel@localhost> (Sami Wagiaalla's message of 	"Fri, 09 Apr 2010 12:05:29 -0400")

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

Sami> I have added tests for all of the above situations.

Thanks.

Sami>     2010-04-09  Sami Wagiaalla  <swagiaal@redhat.com>
Sami>     	PR C++/7943:
Sami>     	* valops.c (find_overload_match): Handle fsym == NULL case.
Sami>     	Add int no_adl argument.
Sami>     	(find_oload_champ_namespace_loop): Call make_symbol_overload_list_adl
[...]

This ChangeLog entry and the one in the patch are different.

Sami> +			  write_exp_elt_sym (NULL); /* Place holder */

A nit, "placeholder" is one word.
Also, end with a period & double space.

Sami> +  while (TYPE_CODE (type) == TYPE_CODE_PTR || TYPE_CODE (type) == TYPE_CODE_REF
Sami> +         || TYPE_CODE (type) == TYPE_CODE_ARRAY)
Sami> +    type = TYPE_TARGET_TYPE (type);

I think you need a check_typedef in the loop.  Otherwise in some
situations with typedefs I think you can end up with type==NULL.

This is ok with those changes.  Thanks. 

Could you submit a followup patch that adds a NEWS entry?

Tom


      reply	other threads:[~2010-04-23 22:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 20:20 Sami Wagiaalla
2010-03-30 20:00 ` Tom Tromey
2010-04-09 16:11   ` Sami Wagiaalla
2010-04-23 22:34     ` 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=m3iq7hx0fu.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