This is the mail archive of the
mailing list for the GCC project.
Re: agressive fixincludes
- To: gcc at gcc dot gnu dot org
- Subject: Re: agressive fixincludes
- From: Per Bothner <per at bothner dot com>
- Date: 23 Nov 1999 09:59:45 -0800
- References: <199911231751.MAA20221@caip.rutgers.edu>
"Kaveh R. Ghazi" <email@example.com> writes:
> IIRC, we fix the headers because -ansi stops gcc from handling //
> comments (?) and thus no platform with // in system headers would work
> with -ansi.
How common is that this actually does anything useful, even with
-ansi? I.e. does it really happen that that people #include header
files containing //-comments in C programs? I guess it can happen on
platforms where the vendor C compiler allows //-comments. But is this
a real problem?
A side note: The fix-includes replacement does not change //-comments
to /*-comments; it completely removes them. I don't think this is
a good idea. The point is academic, however, if we agree to not "fix"
I think fixing //-comments may have made sense when //-comments
were not allowed in Gnu C; now it seems (!) to make very little sense.