From: Michael Snyder <msnyder@cygnus.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] testsuite/gdb.c++/cplusfuncs.{exp,cc}: work with either g++ demangler
Date: Mon, 12 Feb 2001 12:12:00 -0000 [thread overview]
Message-ID: <3A8843E0.F92E0B04@cygnus.com> (raw)
In-Reply-To: <200102112349.PAA20280@bosch.cygnus.com>
Michael Elizabeth Chastain wrote:
>
> This is Sunday Sourceware patch #2, revision 2.
>
> Changes since revision 1:
> - Change wording of ChangeLog with respect to gdb/19.
> - Change one more "char *" to "$dm_type_char_star".
>
> gdb has two g++ demanglers. Currently, this test script works okay on
> the v2 demangler, but gives 83 FAILs with the v3 demangler. This patch
> enhances testsuite/gdb.c++/cplusfuncs.{cc,exp} to work with either
> demangler.
>
> The bulk of the change is handling formatting differences:
>
> old demangler new demangler
> --- --------- --- ---------
> "operator, " "operator,"
> "char *" "char*"
> "int *" "int*"
> "long *" "long*"
> "void *" "void*"
> "foo &" "foo&"
> "unsigned int" "unsigned"
> "void" ""
Michael,
I'm curious why you didn't simply write separate regular expressions,
one to recognize the new demangler style and one to recognize the old,
rather than add all this new mechanics. I'm concerned about the tcl
scripts becoming complicated and difficult to maintain.
Please don't get me wrong -- I very much appreciate both the work
that you're investing and the fact that you're championing this
cause.
next prev parent reply other threads:[~2001-02-12 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 15:49 Michael Elizabeth Chastain
2001-02-12 12:12 ` Michael Snyder [this message]
2001-02-12 12:30 Michael Elizabeth Chastain
[not found] <200102050418.UAA29343@bosch.cygnus.com>
2001-02-14 9:00 ` Fernando Nasser
2001-02-14 9:21 Michael Elizabeth Chastain
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=3A8843E0.F92E0B04@cygnus.com \
--to=msnyder@cygnus.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