From: "Eli Zaretskii" <eliz@elta.co.il>
To: David Carlton <carlton@kealia.com>
Cc: gdb-patches@sources.redhat.com, drow@mvista.com
Subject: Re: [rfa] function overloading and namespaces
Date: Sat, 31 Jan 2004 07:54:00 -0000 [thread overview]
Message-ID: <8011-Fri30Jan2004094929+0200-eliz@elta.co.il> (raw)
In-Reply-To: <m31xphpbd6.fsf@coconut.kealia.com> (message from David Carlton on Fri, 30 Jan 2004 09:58:13 -0800)
> From: David Carlton <carlton@kealia.com>
> Date: Fri, 30 Jan 2004 09:58:13 -0800
>
> Tested on i686-pc-linux-gnu, four different GCC version/options; no
> regressions, the new tests pass on all of them (even stabs, since the
> information that we need is generated by buildsym.c). OK to commit?
I have one clerical comment:
> (overload_list_add_symbol): Fix comment, use
> SYMBOL_{LINKAGE,NATURAL}_NAME.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Please avoid such abbreviations, they make it hard to find references to
the two names in the logs.
next prev parent reply other threads:[~2004-01-31 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 17:58 David Carlton
2004-01-31 7:54 ` Eli Zaretskii [this message]
2004-02-02 16:32 ` David Carlton
2004-02-02 20:09 ` Daniel Jacobowitz
2004-02-02 20:44 ` 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=8011-Fri30Jan2004094929+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=carlton@kealia.com \
--cc=drow@mvista.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