From: David Carlton <carlton@kealia.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Add SYMBOL_SET_LINKAGE_NAME
Date: Wed, 18 Feb 2004 00:20:00 -0000 [thread overview]
Message-ID: <yf2oerx62n0.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20040216212406.GC17141@nevyn.them.org> (Daniel Jacobowitz's message of "Mon, 16 Feb 2004 16:24:06 -0500")
On Mon, 16 Feb 2004 16:24:06 -0500, Daniel Jacobowitz <drow@false.org> said:
> This patch adds a macro, SYMBOL_SET_LINKAGE_NAME, which is used to
> set a symbol's name when the name should not be demangled. Used for
> things like typedefs whose name comes from debug info.
The idea is okay, but I don't like the name all that much. I once had
a goal, which I've admittedly been lax about pursuing recently, that
we would have a very clear distinction between linkage names (which
really did mean names used by the linker) and natural names (i.e. the
names in the source code), to the extent that, if we were to represent
these by different types, then our code would almost compile.
When we're talking about types, however, linkage names don't make much
sense, only natural names. So, while it's true that your macro does
set the field that, in the case of a symbol with both linkage and
natural names, corresponds to the linkage name, that's really an
implementation detail that should be shielded behind this macro.
Having said that, I don't have any great suggestions for a better
name. SYMBOL_SET_NATURAL_NAME? SYMBOL_SET_NATURAL_ONLY_NAME? Hmm.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2004-02-18 0:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 21:24 Daniel Jacobowitz
2004-02-16 21:53 ` Elena Zannoni
2004-02-16 22:57 ` Daniel Jacobowitz
2004-02-16 23:35 ` Paul Hilfinger
2004-02-17 0:05 ` Daniel Jacobowitz
2004-02-17 9:59 ` Paul N. Hilfinger
2004-02-17 15:57 ` Andrew Cagney
2004-02-17 16:01 ` Daniel Jacobowitz
2004-02-17 19:14 ` Elena Zannoni
2004-02-17 19:29 ` Daniel Jacobowitz
2004-02-17 23:10 ` Andrew Cagney
2004-02-18 0:43 ` Elena Zannoni
2004-02-18 1:04 ` Daniel Jacobowitz
2004-02-18 0:20 ` David Carlton [this message]
2004-02-18 0:23 ` Daniel Jacobowitz
2004-02-18 0:27 ` Elena Zannoni
2004-02-18 0:32 ` Daniel Jacobowitz
2004-02-18 0:54 ` Elena Zannoni
2004-02-18 1:06 ` Daniel Jacobowitz
2004-02-18 0:49 ` Paul Hilfinger
2004-02-18 1:27 ` David Carlton
2004-02-18 8:12 ` Paul N. Hilfinger
2004-02-18 16:45 ` David Carlton
2004-02-20 9:32 ` Paul N. Hilfinger
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=yf2oerx62n0.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb-patches@sources.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