From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: [drow-cplus-branch] v3 destructors
Date: Fri, 01 Nov 2002 08:36:00 -0000 [thread overview]
Message-ID: <20021101163729.GA7955@nevyn.them.org> (raw)
I've now added code to the stabs reader to report destructor field names
properly. This changes get_destructor_fn_field_name to use that, but not to
rely on it.
I need to double-check with the HP reader, but I can probably rely on this
now, and kill all physname checks for this purpose. One down, N to go, next
on the hitlist is decode_line_2 once I figure out an approach. Then calling
functions.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-11-01 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 8:36 Daniel Jacobowitz [this message]
2002-11-01 8:43 ` Daniel Jacobowitz
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=20021101163729.GA7955@nevyn.them.org \
--to=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