RE: [PHP-DEV] Extensions calling C++
| From: | John Keiser | Date: | Tue, 11 Jul 2000 05:06:46 +0000 |
| Subject: | RE: [PHP-DEV] Extensions calling C++ | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-24160@lists.php.net to get a copy of this message | ||
In the same vein, on some systems "cc" is a C compiler and "cxx" is a C++
compiler. So the "man" test fails for these as well. I agree, .C is bad
for the case-sensitivity reason.
Just pointing out that this criteria is not good. Well, if you think it is
good, you should probably choose "cxx" because that is the only one that
refers to C++.
--John Keiser
> From: Joey Smith [mailto:joey@joeysmith.com]
>
> I agree with Sascha on this one. .cpp looks like "C Preprocesor" to me...
>
> One reason:
> man cpp
>
> On Sun, 9 Jul 2000, Zeev Suraski wrote the following to Sascha Schumann :
>
> > At 23:47 09/07/2000, Sascha Schumann wrote:
> > >On Sun, 9 Jul 2000, Zeev Suraski wrote:
> > >
> > > > At 23:08 09/07/2000, Sascha Schumann wrote:
> > > > >.cpp sucks, because cpp is the C preprocessor.
> > > >
> > > > Is that a common convention? I don't think gcc generates
> .cpp files (you
> > > > choose which file to redirect it to..?)
> > >
> > >Nope, it is just the name which is misleading. Imagine a file called
> > >foo.lex which is handled by yacc.
> >
> > Well, I for once would have never been mislead by .cpp; I suspect most
> > others would also expect .cpp to be C++ and not a preprocessed C file,
> > going all the way back to the days of Turbo C++.
> >
> > What do the rest of you think?
> >
> > Zeev
> > --
> > Zeev Suraski <zeev@zend.com> http://www.zend.com/
> >
> >
> >
>
>