Re: aclang.m4 problem (Cygwin + VC++)

[Peter Eisentraut]

Akim Demaille writes:

> I don't recall well why we recently chose .cc for C++.  ISTR it was
> because before we used `.C' which is not a good choice in case
> insensitive environments.  Ossama had suggested `.cpp', but I chose
> `.cc' because `locate(1)' on my system found more `.cc' and no `.cpp'.

Minor, relatively unheard-of projects such as KDE use `.cpp', `.cc', *and*
`.C', seemingly about 50/25/25. I have seen `.cpp' used (incorrectly IMHO)
as preprocessed C, instead of `.i', but I don't think that was a compiler
that enforced this. OpenJade uses `.cxx', and I have seen `.c++' as well.

I think you need to be flexible in any case. How about a macro that checks
how many of these the compiler accepts?

-- 
Peter Eisentraut                  Sernanders väg 10:115
[EMAIL PROTECTED]                   75262 Uppsala
http://yi.org/peter-e/            Sweden