From: Daniel Berlin <dberlin@redhat.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Start abstraction of C++ abi's
Date: Sun, 18 Feb 2001 18:05:00 -0000 [thread overview]
Message-ID: <x7pugf4ebr.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <200102190058.QAA20694@bosch.cygnus.com>
Michael Elizabeth Chastain <chastain@cygnus.com> writes:
> Hi Daniel,
>
> > I can make it strncmp, or just check method_name[1], but it doesn't
> > make sense otherwise. It's just seeing if the first letter is a "~" in
> > the actual demangled method name, rather than the mangled name.
>
> Ah, ok. I was wondering why it wasn't part of destructor_prefix_p.
Yeah. I plan on renaming the functions, so that it conveys what it's
really doing, but not until i'm far enough along in the rest of the
abstraction, since some might just go away completely, abstracted into
themselves (IE we might only need this really for the v2 abi), or done
away with in favor of better methods.
In order to minimize the code changes for the moment, so i had a
better chance of getting it approved quickly, I only made a few of the
macros (VTBL_PREFIX_P, DESTRUCTOR_PREFIX_P) into functions, added a
function for something that should have been at least a macro
(constructor prefixes, we had the same damn code copied everywhere,
and it was only somewhat right in a few places), and made it work for
both ABI's. I didn't rename anything, i just lowercased them. :)
next prev parent reply other threads:[~2001-02-18 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 16:58 Michael Elizabeth Chastain
2001-02-18 18:05 ` Daniel Berlin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-19 15:08 Michael Elizabeth Chastain
[not found] <200102192211.OAA18590@bosch.cygnus.com>
2001-02-19 14:32 ` Andrew Cagney
2001-02-19 15:01 ` Daniel Berlin
2001-02-18 16:09 Michael Elizabeth Chastain
2001-02-18 16:51 ` Daniel Berlin
2001-02-18 12:51 Daniel Berlin
2001-02-18 22:52 ` Eli Zaretskii
2001-02-19 0:02 ` Daniel Berlin
2001-02-19 3:06 ` Eli Zaretskii
2001-02-19 6:32 ` Daniel Berlin
2001-02-19 8:48 ` Elena Zannoni
2001-02-19 10:24 ` Daniel Berlin
2001-02-19 11:27 ` Andrew Cagney
2001-02-19 13:17 ` Daniel Berlin
2001-02-19 13:36 ` Andrew Cagney
2001-02-19 14:58 ` Stan Shebs
2001-02-19 15:13 ` Michael Snyder
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=x7pugf4ebr.fsf@dynamic-addr-83-177.resnet.rochester.edu \
--to=dberlin@redhat.com \
--cc=chastain@cygnus.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