[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: etags for C++
From: |
Tak Ota |
Subject: |
Re: etags for C++ |
Date: |
Wed, 20 Feb 2002 23:45:46 -0800 (PST) |
Wed, 20 Feb 2002 23:34:36 -0800 (PST): Tak Ota <address@hidden> wrote:
> Thu, 21 Feb 2002 08:47:11 +0200 (IST): Eli Zaretskii <address@hidden> wrote:
>
> >
> > On Wed, 20 Feb 2002, Richard Stallman wrote:
> >
> > > find . -name "*.[chCH]" -print | etags -
> > >
> > > I suppose use of C++ is very common these days.
> > >
> > > .C and .H were used for C++ files. Has that convention changed?
> >
> > No, it didn't change.
> >
> > However, it's possible that capital .C and .H are not used on
> > case-insensitive filesystems such as on Windows.
>
> GNU make 3.79.1 knows .C, .cc and .cpp as the C++ files. And it seems
> to treat .cc as the canonical one and consolidate .C and .cpp into
> .cc.
Also the following is an excerpt from the info page of gcc version
2.96.
-Tak
For any given input file, the file name suffix determines what kind
of compilation is done:
....
`FILE.cc'
`FILE.cxx'
`FILE.cpp'
`FILE.C'
C++ source code which must be preprocessed. Note that in `.cxx',
the last two letters must both be literally `x'. Likewise, `.C'
refers to a literal capital C.
- etags for C++, Tak Ota, 2002/02/19
- Re: etags for C++, Richard Stallman, 2002/02/20
- Re: etags for C++, Eli Zaretskii, 2002/02/21
- Re: etags for C++, Tak Ota, 2002/02/21
- Re: etags for C++,
Tak Ota <=
- Re: etags for C++, Eli Zaretskii, 2002/02/21
- Re: etags for C++, Tak Ota, 2002/02/21
- Re: etags for C++, Francesco Potorti`, 2002/02/22
- Re: etags for C++, Tak Ota, 2002/02/22
- Re: etags for C++, Andreas Schwab, 2002/02/22
- Re: etags for C++, Richard Stallman, 2002/02/23
- Re: etags for C++, Tak Ota, 2002/02/24
- Re: etags for C++, Richard Stallman, 2002/02/24
- Re: etags for C++, Eli Zaretskii, 2002/02/25
- Re: etags for C++, Francesco Potorti`, 2002/02/25