public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drepper.fsp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/47043] New: allow deprecating enum values Date: Wed, 22 Dec 2010 18:31:00 -0000 [thread overview] Message-ID: <bug-47043-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47043 Summary: allow deprecating enum values Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: drepper.fsp@gmail.com The deprecated is nice and it's use should be expanded. Sometimes enum values have to be deprecated and it would be useful if one could write this: enum { newval, oldval __attribute__ ((deprecated)) }; Any use of 'oldval' should provoke the usual warning.
next reply other threads:[~2010-12-22 18:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-22 18:31 drepper.fsp at gmail dot com [this message] 2010-12-22 18:34 ` [Bug c/47043] " steven at gcc dot gnu.org 2013-01-05 23:31 ` bangerth at gmail dot com 2013-01-05 23:32 ` bangerth at gmail dot com 2015-04-30 8:19 ` mpolacek at gcc dot gnu.org 2015-05-22 9:08 ` mpolacek at gcc dot gnu.org 2015-05-22 9:11 ` mpolacek at gcc dot gnu.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=bug-47043-4@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: 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).