public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51437] GCC should warn on the use of reserved identifier/macro names
Date: Sun, 19 Feb 2012 04:42:00 -0000	[thread overview]
Message-ID: <bug-51437-4-JY5psQfnGa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51437-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51437

Rich Felker <bugdal at aerifal dot cx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugdal at aerifal dot cx

--- Comment #6 from Rich Felker <bugdal at aerifal dot cx> 2012-02-19 04:27:43 UTC ---
I would greatly like to see this as well; actually I was just about to file a
duplicate report when I found this, as a result of finding "struct _Color" in
GIMP source... >_<

I think the system headers issue could be handled very easily, with no false
positives and few false negatives. The heuristic would basically be to flag any
occurrence of reserved names except in header files found in the -isystem path,
or in text resulting from expansion of a macro defined by a header file in the
-isystem path.


  parent reply	other threads:[~2012-02-19  4:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 11:20 [Bug c/51437] New: " vanboxem.ruben at gmail dot com
2011-12-06 11:37 ` [Bug c/51437] " redi at gcc dot gnu.org
2011-12-06 11:50 ` vanboxem.ruben at gmail dot com
2011-12-06 13:34 ` redi at gcc dot gnu.org
2011-12-16 11:55 ` potswa at mac dot com
2012-02-19  4:42 ` bugdal at aerifal dot cx [this message]
2012-02-19  5:48 ` josh at joshtriplett dot org
2012-02-19  6:30 ` bugdal at aerifal dot cx
2012-02-19  8:01 ` josh at joshtriplett dot org
2012-02-19  9:34 ` vanboxem.ruben at gmail dot com
2012-02-19 11:17 ` potswa at mac dot com
2012-02-19 18:57 ` josh at joshtriplett dot org
2012-02-19 18:58 ` josh at joshtriplett dot org
2012-02-19 22:42 ` vanboxem.ruben at gmail dot com
2021-11-18 21:21 ` tkoenig at gcc dot gnu.org
2022-07-24 18:08 ` pavel.morozkin at gmail dot com
2022-09-23 14:24 ` redi at gcc dot gnu.org
2022-09-23 20:20 ` pavel.morozkin at gmail dot com

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=bug-51437-4-JY5psQfnGa@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).