This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [rfa] create testsuite/gdb.cp directory

From: Andrew Cagney <ac131313 at redhat dot com>
To: Michael Elizabeth Chastain <mec at shout dot net>
Cc: carlton at kealia dot com, drow at mvista dot com,gdb-patches at sources dot redhat dot com
Date: Fri, 15 Aug 2003 11:14:36 -0400
Subject: Re: [rfa] create testsuite/gdb.cp directory
References: <200308141818.h7EIIP4N032424@duracef.shout.net>

dc> Why not move all the existing scripts to the new directory?  That's
dc> what I'd prefer.

I'm okay with that.  But it would kill the cvs history of the tests,
and it would hurt people doing 'diff' on test runs from before and
after the change (such as gdb 6 to HEAD, after gdb 6 is released).
It wouldn't hurt my test bed because I use a 1000-line Perl script,
not diff, so I can adapt to test name changes.

So I'll subdivide my proposal:

  (1) Create new directory gdb.cp
  (2) Move all existing tests from gdb.c++ to gdb.cp

I have no objection to (2).  But if anyone objects to (2),
then I still want to do (1), with or without (2).

There should be only one C++ testsuite directory: gdb.c++ XOR gdb.cp. Otherwize general confusion will result and, no matter how good everyones intent, new gdb.c++/* tests will eventually be added.

I'd not put much weight on CVS stupidity. Limitations of the configure tool should not be used as an excuse for failing to fix a problem :-)

enjoy,
Andrew

References:
- Re: [rfa] create testsuite/gdb.cp directory
  - From: Michael Elizabeth Chastain

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]