From: David Carlton <carlton@math.stanford.edu>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com, Jim Blandy <jimb@redhat.com>
Subject: Re: [rfa] SYMBOL_NATURAL_NAME, SYMBOL_LINKAGE_NAME
Date: Tue, 25 Feb 2003 05:04:00 -0000 [thread overview]
Message-ID: <ro1ptph9cig.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <15962.56551.907171.819725@localhost.redhat.com>
On Mon, 24 Feb 2003 22:03:03 -0500, Elena Zannoni <ezannoni@redhat.com> said:
> David Carlton writes:
>> This patch adds macros SYMBOL_NATURAL_NAME and SYMBOL_LINKAGE_NAME to
>> symtab.h. The former returns what the programmer thinks a symbol is
>> called; the latter returns what the linker thinks a symbol is called.
>> In C, these are the same thing; in C++, the former is the demangled
>> name, and the latter is the mangled name.
> Good move. A couple of things. I think the sentence "the
> programmer thinks a symbol is called" is a bit vague. Maybe
> something like the 'name of a symbol as it appears in the high level
> programming language', or 'name of a symbol as it was declared in
> the high level program' or something like that?
Fair enough. Maybe "the name of the symbol as referred to in the
source code"?
> Second thing, more important. I think that if we are going to try to
> switch away from using SYMBOL_NAME, we should be renaming it to
> DEPRECATED_SYMBOL_NAME, because this will be more effective than
> putting a 'suggested use' in a comment. It's a bit more of slog work,
> but we could then even ARI the DEPRECATED_SYMBOL_NAME.
> what do you think?
Absolutely. That'll help other people conform, and encourage me to
take the time to audit uses of the name sooner rather than later.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-02-25 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 1:00 David Carlton
2003-02-25 2:59 ` Elena Zannoni
2003-02-25 3:07 ` Andrew Cagney
2003-02-25 5:04 ` David Carlton [this message]
2003-02-25 21:13 ` David Carlton
2003-02-25 21:27 ` Elena Zannoni
2003-02-25 21:36 ` David Carlton
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=ro1ptph9cig.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.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