Re: Extensions calling C++

At 16:03 11-07-00, Sascha Schumann wrote:

On Tue, 11 Jul 2000, Jade Nicoletti wrote: I'm for .cpp Quoting from the gcc manual:

      .c    C source; preprocess, compile, assemble
      .C    C++ source; preprocess, compile, assemble
      .cc   C++ source; preprocess, compile, assemble
      .cxx  C++ source; preprocess, compile, assemble
      .m    Objective-C source; preprocess, compile, assemble
      .i    preprocessed C; compile, assemble
      .ii   preprocessed C++; compile, assemble

So, cpp is the C Preprocesor, but not the file extention of preprocessed C

    Well, noone said that .cpp is the file extension of
    preprocessed C. But when you deal with the build system, you
    will notice that CPP always refers to the C preprocessor.
    That is an ambiguity which can be avoided IMHO.

I think this ambiguity is something nobody other than the ones involved in the core of the build process would be aware of, let alone care about... The average programmer, even one that develops C++ modules, will not have to touch any CXX autoconf macros - it's just something in the main build process, which will be done once and for all. .cxx is simply ugly, and .cpp is a de-facto standard for C++ files. Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/