Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] C++-ify typedef hash
Date: Tue, 27 Mar 2018 10:33:00 -0000	[thread overview]
Message-ID: <2163f64d-42c9-0a7f-8745-f20a7f8b6c0a@redhat.com> (raw)
In-Reply-To: <878taexlfl.fsf@tromey.com>

On 03/27/2018 04:10 AM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
> 
> Pedro> At least this comment should be updated -- there's no "PRINTERS"
> Pedro> parameter any longer.
> 
> I just removed this comment, since I couldn't think of a useful comment
> to put before a destructor.
> 
>>> +  /* Copy a typedef hash.  */
>>> +  typedef_hash_table (const typedef_hash_table *);
> 
> Pedro> This method's prototype gave me pause -- is there a reason this
> Pedro> isn't a regular copy ctor?
> 
> I've changed it.  I think this was something I meant to do and then
> forgot to complete.
> 
> Pedro> But FLAGS isn't a hash table, right?  The original comment said:
> Pedro>  /* Look up the type T in the typedef hash table in with FLAGS.
> Pedro>                                                  ^^^^^^^
> Pedro> I wonder whether that was a typo for "within".
> Pedro> Maybe this could say something about local/global too.
> 
> I've rewritten this comment, let me know what you think.

LGTM.

Thanks,
Pedro Alves


      reply	other threads:[~2018-03-27 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 21:59 Tom Tromey
2018-03-26 15:13 ` Pedro Alves
2018-03-27  3:11   ` Tom Tromey
2018-03-27 10:33     ` Pedro Alves [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=2163f64d-42c9-0a7f-8745-f20a7f8b6c0a@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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