Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: gcc-patches@gcc.gnu.org, jimb@cygnus.com
Cc: chastain@cygnus.com, dberlin@cygnus.com,
	gdb-patches@sources.redhat.com, samuel@codesourcery.com
Subject: Re: [RFA] Extend demangler to recognize destructors/constructors
Date: Thu, 15 Mar 2001 10:58:00 -0000	[thread overview]
Message-ID: <200103151857.KAA30887@bosch.cygnus.com> (raw)

I like the enums.  But I would like to have an explicit enum for
gnu_v3_not_a_ctor and gnu_v3_not_a_dtor, rather than using a literal
value of 0 which is not in the enum (consider what gdb will show people).

Also in the peek_char / next_char changes, you changed where
the current char is during the call to result_add_string.  I don't
know if that's important.

Michael


             reply	other threads:[~2001-03-15 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 10:58 Michael Elizabeth Chastain [this message]
2001-03-15 11:06 ` Alex Samuel
  -- strict thread matches above, loose matches on Subject: below --
2001-03-15 10:48 Jim Blandy
2001-03-15  1:00 Jim Blandy
2001-03-15  1:15 ` Gabriel Dos Reis

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=200103151857.KAA30887@bosch.cygnus.com \
    --to=chastain@cygnus.com \
    --cc=dberlin@cygnus.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@cygnus.com \
    --cc=samuel@codesourcery.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