From: "Anthony Green" <green@redhat.com>
To: "Jim Blandy" <jimb@cygnus.com>, <gdb-patches@sources.redhat.com>
Subject: RE: abstract C++ ABI dependencies
Date: Tue, 24 Apr 2001 12:20:00 -0000 [thread overview]
Message-ID: <NEBBKJDPKLNNENPPIHCPCEJILBAA.green@redhat.com> (raw)
In-Reply-To: <20010424173019.9FAC85E9CB@zwingli.cygnus.com>
Jim wrote in gdb/jv-typeprint.c:
> ! is_full_physname_constructor =
> is_constructor_name (physname) != 0 || is_destructor_name (physname) != 0;
Actually, it didn't look exactly like that. My mailer is munging it because
it was too long. The patch is fine by me as long as the formatting is
changed.
I also find "is_constructor_name (physname) || is_destructor_name
(physname)" easier to read, but to each his own...
Thanks!
AG
next prev parent reply other threads:[~2001-04-24 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 10:30 RFA: " Jim Blandy
2001-04-24 12:20 ` Anthony Green [this message]
2001-04-24 16:39 ` 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=NEBBKJDPKLNNENPPIHCPCEJILBAA.green@redhat.com \
--to=green@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.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