Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: fnasser@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] testsuite/gdb.c++/cplusfuncs.{exp,cc}: work with either g++ demangler
Date: Wed, 14 Feb 2001 09:21:00 -0000	[thread overview]
Message-ID: <200102141721.JAA29024@bosch.cygnus.com> (raw)

Hi Fernando,

> Also, we must consider that what the tests are really checking for is
> not the presence of one some spaces, but that the right methods were
> found etc. (well, int and void disappearing does hurt a bit, but still,
> that was not what the test was written for).

Right.  As I understand it, this is the autoconf way.  Version checks are
bad, specific feature tests are good.

Last night I checked out the discussion on gcc-patches about Daniel
Berlin's demangler patch.  There's a style discussion going on about
what the demangler should emit with people referring to their style
document, gcc/libstdc++-v3/docs/html/17_intro/C++STYLE.

I will not willingly accept a project dependency on a controversial
decision that belongs to another project.  I'm going to continue
submitting patches that make gdb testsuite work with all known styles.
If the demangler gets more compatible, that's great.

> 1) If we had the "known failures" we could have marked those 8 tests as
>    such and associated with the Gnats id.

We have those bug_id and prms_id fields that are associated with the
whole test.  If someone wants to do some infrastructure work to link to
Gnats, I will be happy to use them.  I like filing Gnats bugs.

> 3) Your patch should have been submitted as 3 separate patches.

Understood.

> 4) Before checking in, please add some of the comments to the test file
>    (see below).  No need to repost.

You got it.

> 5) This is a nitty-picky thing :-) Please add a period after "New file" in
>    your first ChangeLog entry (and capitalize the following letter) before
     checking it in.

Ditto.

> And again, thanks for the patch.

Two down (almost).  Thirteen to go.

Michael


             reply	other threads:[~2001-02-14  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14  9:21 Michael Elizabeth Chastain [this message]
     [not found] <200102050418.UAA29343@bosch.cygnus.com>
2001-02-14  9:00 ` Fernando Nasser
  -- strict thread matches above, loose matches on Subject: below --
2001-02-12 12:30 Michael Elizabeth Chastain
2001-02-11 15:49 Michael Elizabeth Chastain
2001-02-12 12:12 ` 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=200102141721.JAA29024@bosch.cygnus.com \
    --to=chastain@cygnus.com \
    --cc=fnasser@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