public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jyasskin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/44244] New: Provide -f flags to turn on individual C++0x features Date: Sat, 22 May 2010 19:01:00 -0000 [thread overview] Message-ID: <bug-44244-13604@http.gcc.gnu.org/bugzilla/> (raw) Right now, gcc provides --std=c++0x to turn on all the features from C++0x that it's implemented. However, it would be useful for organizations migrating to C++0x to turn on one feature at a time as that feature becomes stable. For example, we might turn on -fenable-c++0x-auto before -fenable-c++0x-lambdas. -- Summary: Provide -f flags to turn on individual C++0x features Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jyasskin at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44244
next reply other threads:[~2010-05-22 19:01 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-22 19:01 jyasskin at gmail dot com [this message] 2010-05-22 19:05 ` [Bug c++/44244] " pinskia at gcc dot gnu dot org 2010-06-04 15:51 ` manu at gcc dot gnu dot org 2010-06-04 17:56 ` jyasskin 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-44244-13604@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).