From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: "gp \>\> \"gdb-patches\@sourceware.org ml\""
<gdb-patches@sourceware.org>
Subject: Re: [RFA] Updated path expression computations for varobj trees
Date: Thu, 12 Jan 2012 21:30:00 -0000 [thread overview]
Message-ID: <m3k44wzkeu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F060266.4070409@redhat.com> (Keith Seitz's message of "Thu, 05 Jan 2012 12:04:54 -0800")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> In other words, we assume that the construct is a compound type unless
Keith> the child's name begins with "*", which means the parent must be a
Keith> pointer.
Keith> We may encounter difficulties with this, too, mind you, but I believe
Keith> this is a cheaper and easier condition to deal with than the regexp.
Me too.
If the issue is typedefs, we also have the option of requiring a certain
naming convention for code using this part of the test suite.
Keith> What do you think?
It is fine by me.
Tom
next prev parent reply other threads:[~2012-01-12 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 23:43 Keith Seitz
2011-12-20 15:25 ` Tom Tromey
2011-12-20 17:48 ` Keith Seitz
2012-01-05 20:05 ` Keith Seitz
2012-01-12 21:30 ` Tom Tromey [this message]
2012-01-12 22:33 ` Keith Seitz
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=m3k44wzkeu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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