From: Daniel Jacobowitz <drow@false.org>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Typedef support for linespecs
Date: Wed, 11 Nov 2009 23:02:00 -0000 [thread overview]
Message-ID: <20091111230149.GA28314@caradoc.them.org> (raw)
In-Reply-To: <4AFB3F69.9070107@redhat.com>
On Wed, Nov 11, 2009 at 02:49:13PM -0800, Keith Seitz wrote:
> ChangeLog
> 2009-11-11 Keith Seitz <keiths@redhat.com>
>
> * linespec.c (lookup_prefix_sym): Lookup the symbol
> in both STRUCT_DOMAIN and VAR_DOMAIN.
>
> testsuite/ChangeLog
> 2009-11-11 Keith Seitz <keiths@redhat.com>
>
> * gdb.cp/classes.cc (ByAnyOtherName): Add typedef and
> use it instead of "Foo".
> * gdb.cp/classes.exp (do_tests): Add a test to access
> a method through a typedef'd class name.
OK. I still hate linespecs, though.
(Seriously... if we figure out that it isn't a file:line, we should
use the normal expression parser for an expression portion of
it... yes, I do realize just how difficult this would be, but the
inconsistencies drive folks mad.)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-11-11 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 22:49 Keith Seitz
2009-11-11 23:02 ` Daniel Jacobowitz [this message]
2009-11-11 23:35 ` 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=20091111230149.GA28314@caradoc.them.org \
--to=drow@false.org \
--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