>>>>> "Peter" == Peter Eisentraut <[EMAIL PROTECTED]> writes:
Peter> Minor, relatively unheard-of projects such as KDE
What is it? ;)
Peter> use `.cpp', `.cc', *and* `.C', seemingly about 50/25/25. I have
Peter> seen `.cpp' used (incorrectly IMHO) as preprocessed C, instead
Peter> of `.i', but I don't think that was a compiler that enforced
Peter> this. OpenJade uses `.cxx', and I have seen `.c++' as well.
Peter> I think you need to be flexible in any case. How about a macro
Peter> that checks how many of these the compiler accepts?
Sounds like a good idea, but anyway I think it's completely useless
without support from Automake.
I think it would be too complex to try to robustly support various
extensions, but robustly I mean to get ready to handle compilers which
do not support the extension which is used.
Rather, we imagine that Automake robustly supports say only .cc. In
that case it should not be too hard to add an extra option to
`compile' which would specify under what name the source file should
be presented to the compiler.
Do all the compiler require an input file name? Can't we use stdin +
#line?
