Re: File extensions for C++ source?

[Gabriel Dos Reis <gdr at integrable-solutions dot net>]

Jim Wilson <wilson@specifixinc.com> writes:

| On Sat, 2003-11-29 at 15:09, Gabriel Dos Reis wrote:
| > I can see how it might be problematic in a very general setting.  But
| > I can't see why that is the case for GCC testsuite?  In what ways is it
| > problematic for GCC testsuite?
| 
| I don't know.  The first example I thought of was a problem with default
| rules in make.

AFAICS, testsuites are run through DejaGnu drivers, and there is no
such things like "default rules in make" being used.

|  If you have both .c.o and .C.o rules, then make will use
| which ever one it tries first because reads are case insensitive. 

Aha, but no such thing exists and I can't see why we would like to
have something like that in the testsuites.

| If
| there is code anywhere in the testsuite that looks for a .c or .C file,
| because it wants to do something different for a C or C++ file, then it
| will find which ever one it looks for first, which would be a problem. 
| I don't know offhand if there is any such code in the testsuites.  If we

No one that I'm aware of, no one that I can think of. 

| already have .C files in the testsuite, and they already work, then
| obviously there is no problem there.

yup.  That is also my sentiment.

Thanks for this detailed reply.

-- Gaby