public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "leor at bdsoft dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/15684] Pointer to member function called on incomplete type should diag Date: Fri, 28 May 2004 14:46:00 -0000 [thread overview] Message-ID: <20040527202927.15891.qmail@sourceware.org> (raw) In-Reply-To: <20040527163621.15684.gianni@mariani.ws> ------- Additional Comments From leor at bdsoft dot com 2004-05-27 20:29 ------- (In reply to comment #5) > I cannot find where in the C++ standard that this is invalid and in the thread it only says that they > contracted EDG, if you think this is an issue, raise it to comp.lang.c++.moderated instead and then > when they decide it is invalid you can reopen this bug. The citation from the standard is (5.5p3): 3 The binary operator ->* binds its second operand, which shall be of type "pointer to member of T" (where T is a completely-defined class type) to its first operand, which shall be of type "pointer to T" or "pointer to a class of which T is an unambiguous and accessible base class." The result is an object or a function of the type specified by the second operand. "where T is a completely-defined class type" is pretty cut-and-dried. Plus, as John Spicer has indicated to me in a private email: "An implementation could choose different forms of pointer-to-member representations depending on whether or not the class had virtual functions, or something like that. In such implemenations, a complete type would be needed to get correct behavior." -leor -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15684
next prev parent reply other threads:[~2004-05-27 20:29 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-28 1:47 [Bug c++/15684] New: " gianni at mariani dot ws 2004-05-28 1:55 ` [Bug c++/15684] " gianni at mariani dot ws 2004-05-28 2:01 ` pinskia at gcc dot gnu dot org 2004-05-28 4:00 ` leor at bdsoft dot com 2004-05-28 4:01 ` pinskia at gcc dot gnu dot org 2004-05-28 11:31 ` gianni at mariani dot ws 2004-05-28 11:57 ` pinskia at gcc dot gnu dot org 2004-05-28 12:02 ` pinskia at gcc dot gnu dot org 2004-05-28 14:46 ` leor at bdsoft dot com [this message] 2004-05-28 15:45 ` pinskia at gcc dot gnu dot org 2004-05-28 15:59 ` gianni at mariani dot ws 2004-05-28 17:01 ` leor at bdsoft dot com 2004-05-28 17:55 ` giovannibajo at libero dot it 2004-05-28 19:03 ` pinskia at gcc dot gnu dot org 2004-05-28 19:13 ` pinskia at gcc dot gnu dot org 2004-12-10 21:09 ` pinskia at gcc dot gnu dot org 2004-12-10 21:41 ` pinskia at gcc dot gnu dot org [not found] <bug-15684-2828@http.gcc.gnu.org/bugzilla/> 2007-06-20 13:44 ` pinskia at gcc dot gnu dot org [not found] <bug-15684-4@http.gcc.gnu.org/bugzilla/> 2021-07-16 7:55 ` redi 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=20040527202927.15891.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).