Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [rfa] create testsuite/gdb.cp directory
Date: Thu, 14 Aug 2003 18:10:00 -0000	[thread overview]
Message-ID: <200308141810.h7EIALlu032266@duracef.shout.net> (raw)

This is a formal proposal to create a new directory, testsuite/gdb.cp,
for c++ tests.  This proposal is for HEAD only, not gdb_6_0-branch.

The issue is that "gdb.c++" contains characters which are not permitted
on MS-DOS filenames.  So *every* file in testsuite/gdb.c++ must have an
entry in config/djgpp/fnchange.lst.  I would like to get away from that
requirement and use plain directory names that just work everywhere.

I propose to use testsuite/gdb.cp for new C++ test scripts only.
Existing scripts would remain in gdb.c++.

'cp' is the same name that other C++ files in gdb have,
such as cp-abi.c, cp-namespace.c, and cp-support.c.
Also libiberty/cp-demangle.c.

I am proposing this because I want to add a test script for
pr gdb/186, which has been open for two years and is still broken
with gdb HEAD.  I'd like to start adding new test scripts to
the new directory, so I'm coming here to create the new directory.

'cvs add' with a directory name is irreversible (with cvs commands
at least) so I am making a formal application to do this.

Okay to create new directory gdb/testsuite/gdb.cp in HEAD ?

Michael C


             reply	other threads:[~2003-08-14 18:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14 18:10 Michael Elizabeth Chastain [this message]
2003-08-14 18:12 ` David Carlton
2003-08-14 18:12 ` Daniel Jacobowitz
2003-08-14 18:18 Michael Elizabeth Chastain
2003-08-15 15:52 ` Andrew Cagney
2003-08-15 15:34 Michael Elizabeth Chastain
2003-08-15 15:48 ` David Carlton

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=200308141810.h7EIALlu032266@duracef.shout.net \
    --to=mec@shout.net \
    --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