> Nope, I think this is a case where we should mandate an extension. > For instance, I'm very much for .f77 for Fortran 77, and not .f, so > that for instance Automake knows what is the compiler to run if there > is F77, F90 and the preprocessed variations. The de-facto standard seems to be that FORTRAN files end in .f if they do not need preprocessing and .F if they need it. Most F77 compilers I know of (mainly on unix and windows) understand those, or cannot do useful preprocessing so only the first one applies. The latter is the case on windows with df (and file system case insensitivity is not a problem). I would not recommend deviating from that convention unless someone can provide a list of the extensions compilers support and another suffix (e.g. .f77) stands out. I would also recommend against .C as the C++ file extension -- VC++ is a combined C and C++ compiler and the file system is case insensitive. (Alternatively, autoconf should use the -Tc/-Tp options with that compiler to explicitly set the language.) .cc and .cxx seem to be widely accepted C++ extensions, for some reason I have the recollection that .cpp isn't quite as widely understood. IMHO there shouldn't be a restriction to a single extension though; all three of .cc, .cxx and .cpp are all quite acceptable and projects should be free to choose the conventions. Cheers, //lat -- History teaches us that men and nations behave wisely once they have exhausted all other alternatives. --Abba Eban
