This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Warnings about rcs_id strings: let's settle this
- From: "Kean Johnston" <jkj at sco dot com>
- To: "'Joseph S. Myers'" <jsm28 at cam dot ac dot uk>
- Cc: "'Zack Weinberg'" <zack at codesourcery dot com>,"'Joe Buck'" <jbuck at synopsys dot com>, <gcc at gcc dot gnu dot org>
- Date: Fri, 2 May 2003 12:03:40 -0700
- Subject: RE: Warnings about rcs_id strings: let's settle this
- Organization: The SCO Group
> Addition of const is an easy modification.
Indeed. Omitting it is even easier :)
As I stated in my previous mail, the regression was what
drew attention to the issue, it doesn't define it. I *HAVE* been
bothered by this but I wrote a sed script to trim the warning
messages down (I compile -Wall not -Wall -Werror yet). I would
LIKE to use -Werror, but the fact that the SVR3.2 code is so
riddled with static char *sccsid crap prevents that. I think
the intent is to get this warning to do the right thing, not
just solve one regression case. Sometimes (read: often) when
you fix one regression bug you solve more than one problem
in the fix. This is such a time. Let me state this another way.
What is the *HARM* in checking non-const.
I know Joe agrees with me, and others seem ambivalent. Tell you
what ... this debate can rage for ages. I'm going to make it
NOT check constedness, unless that would veto the entire patch.
Kean