public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/4902: no macro redef warnings Date: Thu, 15 Nov 2001 08:16:00 -0000 [thread overview] Message-ID: <20011120081602.23169.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR preprocessor/4902; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Neil Booth <neil@daikokuya.demon.co.uk> Cc: "Golubev I. N." <gin@mo.msk.ru>, gcc-gnats@gcc.gnu.org Subject: Re: preprocessor/4902: no macro redef warnings Date: Tue, 20 Nov 2001 00:08:53 -0800 On Tue, Nov 20, 2001 at 07:51:43AM +0000, Neil Booth wrote: > > Neil wrote in <http://gcc.gnu.org/ml/gcc-bugs/2001-11/msg00263.html>: > > > > > you get a warning iff -pedantic > > > > `(cpp)Undefining and Redefining Macros' does not say so. Neither does > > it explain (or refer to explanation) why that change of requiring > > `-pedantic' was made (making `gcc' different from many other compilers > > which warn by default). > > > > Perhaps some people think that redefn warnings `trigger frequently on > > harmless code' (as `-pedantic' description in `(cpp)Invocation' says), > > but I disagree. My experience shows that more often than not they > > detect real bugs. > > What do you think, Zack? This warning was on by default in 2.95, and I agree with the reporter that non-trivial redefinitions do tend to represent bugs. warn_of_redefinition is your code, so I must presume you meant to change it - why? zw
next reply other threads:[~2001-11-20 8:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-11-15 8:16 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-19 9:56 neil 2001-11-19 9:48 neil 2001-11-19 9:46 Neil Booth 2001-11-16 23:46 Neil Booth 2001-11-15 7:46 Neil Booth 2001-11-13 15:26 Golubev I. N.
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20011120081602.23169.qmail@sourceware.cygnus.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).