public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/7654] warn if an enum is being assigned a non enum value Date: Fri, 15 Feb 2008 10:36:00 -0000 [thread overview] Message-ID: <20080215103613.28530.qmail@sourceware.org> (raw) In-Reply-To: <bug-7654-1366@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from manu at gcc dot gnu dot org 2008-02-15 10:36 ------- It is not clear whether we want such a warning or not (and in 6 years, just 2 people have suggested it not too loudly). But if we do: * -Wstrict-enums seems a better name. It should be consistent and not handle only assignments but also argument passing. * An explicit cast should suppress the warning. * The warning should not be enabled by -Wall and probably neither by -Wextra because enums are *correctly* used as integers by C programmers. It is also unclear whether we want to warn for any integer/enum assigned to a different enum type or just for integers/enums outside the range of a particular enum type. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|-Wenum-assignment : Warn if |warn if an enum is being |an enum is being assigned a |assigned a non enum value |non enum value | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7654
next prev parent reply other threads:[~2008-02-15 10:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-7654-1366@http.gcc.gnu.org/bugzilla/> 2008-02-15 10:25 ` [Bug c/7654] -Wenum-assignment : Warn " manu at gcc dot gnu dot org 2008-02-15 10:36 ` manu at gcc dot gnu dot org [this message] 2008-08-24 21:32 ` [Bug c/7654] warn " manu at gcc dot gnu dot org
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=20080215103613.28530.qmail@sourceware.org \ --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: 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).