From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [3/3] RFC: tag name completion
Date: Mon, 10 Dec 2012 15:08:00 -0000 [thread overview]
Message-ID: <87vccarllc.fsf@fleche.redhat.com> (raw)
In-Reply-To: <50C269D3.10306@redhat.com> (Pedro Alves's message of "Fri, 07 Dec 2012 22:12:35 +0000")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> I'm not that much familiar with this part of the code. I'm just
Pedro> wondering about struct vs class. GDB treats both mostly
Pedro> interchangeably, e.g., with "struct ABC {};", ptype "class ABC"
Pedro> will find and print the struct. Would "class A<tab>" still
Pedro> complete to "class ABC" with this patch?
It will work because:
#define TYPE_CODE_CLASS TYPE_CODE_STRUCT
I think we should probably just drop this and always use TYPE_CODE_STRUCT.
Tom
prev parent reply other threads:[~2012-12-10 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 18:43 Tom Tromey
2012-12-07 20:06 ` Tom Tromey
2012-12-07 22:12 ` Pedro Alves
2012-12-10 15:08 ` 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=87vccarllc.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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