public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59193] Unused postfix operator temporaries Date: Tue, 19 Nov 2013 16:41:00 -0000 [thread overview] Message-ID: <bug-59193-4-ufLABSgeIA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59193-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59193 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- I see nothing at http://gcc.gnu.org/codingconventions.html that would apply such a C++ coding practice to the mostly C-like code in GCC. Changes to coding conventions should be proposed on the gcc@gcc.gnu.org mailing list, not in Bugzilla; the mailing list is a better place to get consensus on such things and Bugzilla is better for things that are unambiguously bugs rather than stylistic or possibly controversial. Personally I think such changes are pointless when ordinary C integer / pointer types are in use.
next parent reply other threads:[~2013-11-19 16:41 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-59193-4@http.gcc.gnu.org/bugzilla/> 2013-11-19 16:41 ` joseph at codesourcery dot com [this message] 2013-11-20 0:59 ` pinskia at gcc dot gnu.org 2014-02-05 9:07 ` mpolacek at gcc dot gnu.org 2014-02-12 19:22 ` mtewoodbury at gmail dot com 2014-02-12 19:30 ` pinskia at gcc dot gnu.org 2014-02-19 6:15 ` mtewoodbury at gmail dot com 2014-02-19 9:58 ` pinskia at gcc dot gnu.org 2014-02-19 10:18 ` jakub at gcc dot gnu.org 2014-02-20 2:48 ` mtewoodbury at gmail dot com 2014-02-20 6:15 ` pinskia at gcc dot gnu.org 2014-02-22 2:03 ` mtewoodbury at gmail dot com 2014-02-22 4:19 ` pinskia at gcc dot gnu.org 2014-02-22 11:10 ` mtewoodbury at gmail dot com 2014-06-25 11:27 ` 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-59193-4-ufLABSgeIA@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).