Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!tdatirv!sarima
From: sarima@tdatirv.UUCP (Stanley Friesen)
Newsgroups: comp.lang.c++
Subject: Re: best extension for C++ files
Message-ID: <144@tdatirv.UUCP>
Date: 10 Sep 90 16:32:05 GMT
References: <907@zinn.MV.COM> <1845@cs.rit.edu> <3358@stl.stc.co.uk> <1990Sep08.094000.10269@virtech.uucp>
Reply-To: sarima@tdatirv.UUCP (Stanley Friesen)
Organization: Teradata Corp., Irvine
Lines: 13

In article <1990Sep08.094000.10269@virtech.uucp> rdg@virtech.uucp (Roger D. Gough) writes:
>Maybe this would simply add to the confusion, but why not just use '.c'
>and '.h', and let whoever needs to know look in the makefile (or equivalent)
>to see how CC is defined, etc.

The big problem with this is when one needs to *mix* C and C++ sources in a
single project (as, for instance, in converting from C to C++ on an existing
product).  In this case the *single* makefile needs to be able to tell for
each source file whether it is C or C++ to call the right compiler.
(And due to differences in the semantics of prototypes, the correct compiler
must be called)
----------------------------
uunet!tdatirv!sarima					(Stanley Friesen)