From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19371 invoked by alias); 6 Dec 2011 11:20:18 -0000 Received: (qmail 19362 invoked by uid 22791); 6 Dec 2011 11:20:17 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Dec 2011 11:20:04 +0000 From: "vanboxem.ruben at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/51437] New: GCC should warn on the use of reserved identifier/macro names Date: Tue, 06 Dec 2011 11:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: vanboxem.ruben at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-12/txt/msg00555.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51437 Bug #: 51437 Summary: GCC should warn on the use of reserved identifier/macro names Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: vanboxem.ruben@gmail.com For C and C++, Clang should warn when user code uses identifiers or macros that are implementation-reserved. For C(99), this would mean names starting with an underscore followed by another unerscore or capitalized letter. For C++ a single underscore is also reserved for the global namespace. I could have messed the above rules up, but these are the cause of a lot of unexpected bugs, and a warning would be super-easy to implement.