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: bkorb at sco dot COM
- Subject: Re: Still a lot of C++ files getting "fixed"
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Wed, 26 Jan 2000 12:47:48 -0500 (EST)
- Cc: austern at isolde dot engr dot sgi dot com, austern at sgi dot com, autogen at linuxbox dot com, gcc-bugs at gcc dot gnu dot org, mark at codesourcery dot com, martin at loewis dot home dot cs dot tu-berlin dot de
> From: Bruce Korb <bkorb@sco.COM>
>
> "Kaveh R. Ghazi" wrote:
> >
> > If we decide not to fix // comments in system headers, then IMHO, we
> > cannot have -pedantic *reject* // in system headers. Otherwise
> > -pedantic becomes useless for systems which have this problem.
> > [[...]]
> > So I don't think we should even warn about it. I can't imagine a
> > system header would have a "foo //**/bar" type problem, and if it does
> > then we fix *that* header like Bruce said.
>
> You can warn about anything with -Wall, otherwise
> you are completely correct.
But then -Wall becomes needlessly noisy on platforms with // in system
headers.
IMHO, if we don't fix the headers, then we should always silently
accept // in system headers, regardless of what flags are set.
Whether we take action on *user* code is entirely different.
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions