public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/4902: no macro redef warnings
Date: Thu, 15 Nov 2001 07:46:00 -0000	[thread overview]
Message-ID: <20011120075601.26309.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR preprocessor/4902; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.demon.co.uk>
To: "Golubev I. N." <gin@mo.msk.ru>
Cc: gcc-gnats@gcc.gnu.org, Zack Weinberg <zack@codesourcery.com>
Subject: Re: preprocessor/4902: no macro redef warnings
Date: Tue, 20 Nov 2001 07:51:43 +0000

 > 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?
 
 Neil.


             reply	other threads:[~2001-11-20  7:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15  7:46 Neil Booth [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  8:16 Zack Weinberg
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=20011120075601.26309.qmail@sourceware.cygnus.com \
    --to=neil@daikokuya.demon.co.uk \
    --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: link
Be 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).