This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: agressive fixincludes
- To: Per Bothner <per at bothner dot com>
- Subject: Re: agressive fixincludes
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 23 Nov 1999 11:05:20 -0700
- cc: gcc at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <m2r9hhdr72.fsf@magnus.bothner.com>you write:
> "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> 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?
Unfortunately it happens all the time in vendor include files.
jeff