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: Gabriel Dos Reis <dosreis at cmla dot ens-cachan dot fr>
- Date: 23 Nov 1999 19:22:13 +0100
- Cc: gcc at gcc dot gnu dot org
- Organization: CMLA, ENS Cachan -- CNRS URA 1611 (France)
- References: <199911231751.MAA20221@caip.rutgers.edu> <m2r9hhdr72.fsf@magnus.bothner.com>
- Reply-To: gcc at gcc dot gnu dot org
Per Bothner <per@bothner.com> writes:
| "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 can't really tell, but for the record C99 allows //-comments.
-- Gaby