public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "herring at lanl dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/44402] Doesn't allow friend declarations using a typedef for function type Date: Fri, 26 Aug 2022 15:07:55 +0000 [thread overview] Message-ID: <bug-44402-4-8J9p7ilDoE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44402-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44402 S. Davis Herring <herring at lanl dot gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |herring at lanl dot gov --- Comment #1 from S. Davis Herring <herring at lanl dot gov> --- Current trunk still rejects this, but now produces <source>:3:21: error: invalid use of qualified-name 'A::f' 3 | struct B { friend F A::f; }; | ^
prev parent reply other threads:[~2022-08-26 15:07 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44402-4@http.gcc.gnu.org/bugzilla/> 2013-05-21 23:14 ` paolo.carlini at oracle dot com 2022-08-26 15:07 ` herring at lanl dot gov [this message]
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-44402-4-8J9p7ilDoE@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).