From: Andrew Cagney <cagney@gnu.org>
To: Paul Hilfinger <hilfingr@gnat.com>
Cc: jimb@redhat.com, drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: Abstracting "name"
Date: Fri, 21 May 2004 19:10:00 -0000 [thread overview]
Message-ID: <40AE5414.4030207@gnu.org> (raw)
In-Reply-To: <20040520101812.D99DDF2A0D@nile.gnat.com>
[Subject changed from Re: [RFA] Introduce notion of "search name"]
Andrew Cagney wrote:
Just like the frame, arch, and regcache code, this won't be easy or
simple - it will take multiple iterations and true long term commitment
to GDB.
What we do need to do is recognize the real value in perusing this
strategy (screwing down and better defining interfaces), and that it is
a strategy we can't afford to postpone. Can we do that?
I'm all for good interfaces. The first step here, it seems to me, is to
understand better just what we want out of such an interface---a
requirements memo or API sketch. Andrew has so far listed the following:
symtab_name_put (symbol, ui_file):
Write the printable name to the specified output.
symtab_demangled_cmp (block, symbol, symbol):
Compare two symbols returning their relative position.
[Actually, Andrew's name for this last was "symtab_demanged_cmp", which is
appealing, but perhaps too likely to provoke remark. :->)] Presumably,
you'd also need various functions such as
symtab_*_name_matches (char*, symbol)
(const char * :-)
FYI, another long term objective is to make published symbol objects a
flyweight. Stop trying to differentiate between full and partial
symbols (except within the symtab code) and stop dictating that there's
this two stage load.
Andrew
where * has a number of replacements indicating the type of match desired
(literal, demangled, etc.). Or there could be one of these with an
extra modifier parameter. I presume the dictionary module is
to be folded into this; will this require a symtab_hash_value (symbol)
operation? Also, what will clients want to do with structured names?
Paul Hilfinger
next prev parent reply other threads:[~2004-05-21 19:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 19:15 [RFA] Introduce notion of "search name" Paul Hilfinger
2004-03-19 0:09 ` David Carlton
2004-03-03 19:26 ` David Carlton
2004-03-19 0:09 ` Paul Hilfinger
2004-03-04 8:45 ` Paul Hilfinger
2004-03-19 0:09 ` Paul Hilfinger
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-05 3:59 ` Daniel Jacobowitz
2004-03-05 10:39 ` Paul Hilfinger
2004-03-19 0:09 ` Paul Hilfinger
2004-03-31 22:12 ` Daniel Jacobowitz
2004-04-01 14:53 ` Jim Blandy
2004-04-01 15:00 ` Daniel Jacobowitz
2004-04-01 15:21 ` Jim Blandy
2004-04-02 9:30 ` Paul Hilfinger
2004-04-02 22:27 ` Jim Blandy
2004-04-03 12:04 ` Paul Hilfinger
2004-04-06 14:37 ` Jim Blandy
2004-04-02 9:33 ` Paul Hilfinger
2004-04-02 8:29 ` Paul Hilfinger
2004-04-09 22:40 ` Daniel Jacobowitz
2004-04-12 8:22 ` Paul Hilfinger
2004-04-16 4:11 ` Jim Blandy
2004-04-29 10:37 ` Paul Hilfinger
[not found] ` <20040429211458.GB27523@nevyn.them.org>
[not found] ` <vt2n04umj8b.fsf@zenia.home>
[not found] ` <20040430084538.ECDE1F2E1C@nile.gnat.com>
[not found] ` <20040430134955.GA15786@nevyn.them.org>
2004-05-03 8:49 ` Paul Hilfinger
2004-05-11 19:48 ` Daniel Jacobowitz
2004-05-12 11:00 ` Paul Hilfinger
2004-05-12 13:27 ` Daniel Jacobowitz
2004-05-12 14:14 ` Andrew Cagney
2004-05-12 14:23 ` Daniel Jacobowitz
2004-05-12 15:11 ` Andrew Cagney
2004-05-12 16:59 ` Joel Brobecker
2004-05-13 14:29 ` Andrew Cagney
2004-05-13 9:30 ` Paul Hilfinger
2004-05-13 13:49 ` Daniel Jacobowitz
2004-05-18 21:59 ` Jim Blandy
2004-05-19 9:55 ` Paul Hilfinger
2004-05-19 13:00 ` Daniel Jacobowitz
2004-05-19 15:21 ` Andrew Cagney
2004-05-20 10:18 ` Abstracting "name" Paul Hilfinger
2004-05-21 19:10 ` Andrew Cagney [this message]
2004-05-21 20:01 ` Jim Blandy
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=40AE5414.4030207@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hilfingr@gnat.com \
--cc=jimb@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