From: Tom Tromey <tromey@redhat.com>
To: sami wagiaalla <swagiaal@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: Template function support
Date: Thu, 10 Jun 2010 19:43:00 -0000 [thread overview]
Message-ID: <m3hbla8yid.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C11323B.9030302@redhat.com> (sami wagiaalla's message of "Thu, 10 Jun 2010 14:43:07 -0400")
>>>>> "Sami" == sami wagiaalla <swagiaal@redhat.com> writes:
Sami> I thought I would wright a summery of what I have been up to since
Sami> this work has taken a while now.
Thanks!
Sami> To fix this problem I plan to take a suggestion made by Tom which is
Sami> to add a meta variable corresponding to a group of instance of the
Sami> same template. This variable will enable the consumer of the lookup
Sami> (printing code, evaluation code, overload resolution code, or
Sami> breakpoint code) to do something sensible when this type of symbol is
Sami> encountered.
I thought perhaps you'd have a new LOC_TEMPLATE, then add a new symbol
with that class. Then when you do a lookup for "foo" you can tell that
it is a "phony" symbol that represents a template. Finally, the
symbol's value union could have a new field that points to all the
instantiations.
Alternatively such a symbol could just store a type that has a new
TYPE_CODE_. I'm not sure whether this would be any better.
I'm not sure that this is sane and/or easily implemented.
Sami> + return c != NULL && strchr (name, '>') > c;
I don't think you really need that second clause there.
I didn't look too closely at all of it. Make sure that psymbol changes
don't poison the bcache, and that lookups that find a name like this
don't do the wrong thing elsewhere in gdb.
Tom
next prev parent reply other threads:[~2010-06-10 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 18:57 sami wagiaalla
2010-06-10 19:00 ` Keith Seitz
2010-06-10 19:11 ` Tom Tromey
2010-06-10 19:21 ` Keith Seitz
2010-06-11 3:32 ` Tom Tromey
2010-06-11 14:23 ` sami wagiaalla
2010-06-10 19:17 ` sami wagiaalla
2010-06-10 19:43 ` Tom Tromey [this message]
2010-06-10 20:04 ` sami wagiaalla
2010-06-11 3:29 ` Tom Tromey
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=m3hbla8yid.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).