This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: 3.2/3.3/3.4 Lookup in Nested Class
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Mike Stump <mstump at apple dot com>
- Cc: Jeffrey Oldham <oldham at codesourcery dot com>, gcc-patches at gcc dot gnu dot org, pfeifer at dbai dot tuwien dot ac dot at
- Date: 28 Jan 2003 22:37:09 +0100
- Subject: Re: 3.2/3.3/3.4 Lookup in Nested Class
- Organization: Integrable Solutions
- References: <12CB17F1-3303-11D7-8309-003065A77310@apple.com>
Mike Stump <mstump@apple.com> writes:
| On Tuesday, January 28, 2003, at 11:24 AM, Gabriel Dos Reis wrote:
| > Jeffrey Oldham <oldham@codesourcery.com> writes:
| >
| > | Gabriel Dos Reis wrote:
| > | > Jeffrey Oldham <oldham@codesourcery.com> writes:
| > | > Hi,
| > | > | Index: g++.old-deja/g++.other/lookup24.C
| > | > Ideally, new testcases should go in g++.dg.
| > |
| > | I used the documentation in gcc/testsuite/README to guide where I
| > | placed the new test. It says "almost all C++ tests reside in
| > | subdirectories of g++.old-deja" and "Tests that want to use the
| > normal
| > | dg.exp driver can be put in g++.dg instead. This may be required for
| > | platform-specific tests, or tests with other special requirements."
| > | If this is wrong, would someone please revise it?
| >
| > Yes, I think the documentation is wrong.
|
| I don't think so.
Some time ago, we had a discussion and agreed that all new testcases
should go under g++.dg. That is even why some of us (Jason mostly)
spent time in the g++.dg stuff.
-- Gaby