public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9687: The & operator does not accept parentheses on operand Date: Sat, 15 Feb 2003 12:16:00 -0000 [thread overview] Message-ID: <20030215121600.8211.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9687; it has been noted by GNATS. From: Nathan Sidwell <nathan@codesourcery.com> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, marc.durantez@jp.sony.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/9687: The & operator does not accept parentheses on operand Date: Sat, 15 Feb 2003 12:07:48 +0000 bangerth@dealii.org wrote: > Synopsis: The & operator does not accept parentheses on operand > > State-Changed-From-To: open->closed > State-Changed-By: bangerth > State-Changed-When: Fri Feb 14 21:33:11 2003 > State-Changed-Why: > The C++ standard even has wording to disallow using parentheses. > > Previous versions of gcc accepted the code erroneously. This > has been fixed. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9687 Are you sure? &(T::member) is disallowed, but I don't think &(random_expr) is. Could you explain your deduction to me? FWIW, I think this is a parse error as (MyClass ()) looks like a cast expression to function type, without the trailing expr. I.e. It thought it was seeing (MyClass ())thing I fixed this in the new parser. nathan -- Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC The voices in my head said this was stupid too nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next reply other threads:[~2003-02-15 12:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-15 12:16 Nathan Sidwell [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-17 19:06 Wolfgang Bangerth 2003-02-14 21:33 bangerth 2003-02-13 9:16 marc.durantez
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=20030215121600.8211.qmail@sources.redhat.com \ --to=nathan@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).