AFAIK .cpp is the most portable C++ extension. The Mozilla and ACE (hi
Ossama:) people settled on it for that reason.
It is something akin to slow torture to get VC++ using .cc (requires
registry mangling etc). BCB 4 won't use .cc at all.
Alex.
Lars J. Aas writes:
> On Wed, Jul 19, 2000 at 01:43:58PM +0200, Lars J. Aas wrote:
> : On Wed, Jul 19, 2000 at 12:24:08PM +0200, Akim Demaille wrote:
> : : Mo, Lars, could you give a look at the patch 25-* and see if it works?
> : :
> : : 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'.
> : :
> : : I don't know if moving to .cpp is safe everywhere. Hence this patch.
> :
> : I did a grep on conftest.cc in configure, and still got two redirections
> : and two compilations with that filename. All those are explicitly set
> : in aclang.m4 without use of $ac_ext. The Cygwin-test failed for MSVC++
> : too.
>
> BTW, I believe it was on one of those explicit filename tests it failed,
> IIRC.
>
> Lars J
