This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Still a lot of C++ files getting "fixed"
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: Still a lot of C++ files getting "fixed"
- From: Bruce Korb <bkorb at sco dot COM>
- Date: Tue, 25 Jan 2000 05:33:16 -0800
- CC: gcc-bugs at gcc dot gnu dot org
- Organization: Santa Cruz Operation
- References: <20000124141843S.mitchell@codesourcery.com>
- Reply-To: Bruce Korb <autogen at linuxbox dot com>
Mark Mitchell wrote:
>
> I'm still seeing a lot of C++ source-files getting "fixed" by having
> double-slash comments removed. Here are some more clues that a file
> is a C++ file:
>
> #pragma interface
> #pragma implementation
> class
> public:
> private:
> protected:
'class' is probably not a good choice, unless
there is a fairly easy way to ensure it is used
as a keyword. It would be nice if C++ headers
that got installed as a .h file under /usr/include
had _some_ simple distinguishing characteristic.
Quite the nuisance! :-)
Actually, there is another possibility:
Only strip C++ comments from files found
in a limited set of directories.
What would that set be? Obviously
/usr/include
/usr/include/sys
What other directories contain files that are
actually problems?