public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at cs dot tamu dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/25814] Request for warning for parser ambiguity of function declarations and variable declarations with initializations Date: Tue, 17 Jan 2006 04:01:00 -0000 [thread overview] Message-ID: <20060117040103.2454.qmail@sourceware.org> (raw) In-Reply-To: <bug-25814-5307@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from gdr at cs dot tamu dot edu 2006-01-17 04:01 ------- Subject: Re: Request for warning for parser ambiguity of function declarations and variable declarations with initializations "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes: | Maybe if more C++ books actually talked about this issue, there would not be a | problem (sorry I could not resists). C++ books do take about it -- just check out the good ones. This very problem, if you check out writings from Bjarne or me (see, e.g., our proposal for "generalized initializer list" for discussions), is a problem inherited from the C syntax which permits redundant parenthesis in declarations, exacerbed by the functional notation. Check out details from D&E. | Also warning about very valid and defined | code even if it is a common mistake that beginers make. I would rather have | people actually taught this rule than GCC warning about it. this is somehow hard to diagnose, but I guess one could engineer the front-end to remember redundant parens, but it would be rather low priority for me. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25814
next prev parent reply other threads:[~2006-01-17 4:01 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-17 0:42 [Bug c++/25814] New: Request for new warning Raimund dot Merkert at baesystems dot com 2006-01-17 0:58 ` [Bug c++/25814] Request for warning for parser ambiguity of function declarations and variable declarations with initializations pinskia at gcc dot gnu dot org 2006-01-17 4:01 ` gdr at cs dot tamu dot edu [this message] 2006-01-17 12:33 ` Raimund dot Merkert at baesystems dot com 2006-02-02 19:54 ` pinskia at gcc dot gnu dot org 2006-03-08 5:07 ` bangerth at dealii dot org 2006-11-14 15:36 ` wolfgang dot roemer at gmx dot net 2006-11-14 15:52 ` Raimund dot Merkert at baesystems dot com [not found] <bug-25814-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 11:59 ` jakub at gcc dot gnu.org 2020-08-26 12:22 ` mpolacek at gcc dot gnu.org 2020-08-27 11:12 ` dmalcolm at gcc dot gnu.org 2020-08-27 14:33 ` mpolacek at gcc dot gnu.org 2020-10-22 15:02 ` mpolacek at gcc dot gnu.org 2020-11-05 20:56 ` cvs-commit at gcc dot gnu.org 2020-11-05 20:59 ` 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=20060117040103.2454.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).