public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ehrhardt at mathematik dot uni-ulm dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/6628] cannot typedef const functions Date: Wed, 13 Aug 2003 18:27:00 -0000 [thread overview] Message-ID: <20030813182752.6681.qmail@sources.redhat.com> (raw) In-Reply-To: <20020510135600.6628.ge@cs.twsu.edu> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6628 ehrhardt at mathematik dot uni-ulm dot de changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|0000-00-00 00:00:00 |2003-08-13 18:27:52 date| | ------- Additional Comments From ehrhardt at mathematik dot uni-ulm dot de 2003-08-13 18:27 ------- Reopened based on http://gcc.gnu.org/ml/gcc-bugs/2003-08/msg01573.html: The following piece of code taken directly from the standard (9.3) shows that the typedef should be legal. ============= cut ===================== typedef void fv(void); typedef void fvc(void) const; struct S { fv memfunc1; // equivalent to: void memfunc1(void); void memfunc2(); fvc memfunc3; // equivalent to: void memfunc3(void) const; }; fv S::* pmfv1 = &S::memfunc1; fv S::* pmfv2 = &S::memfunc2; fvc S::* pmfv3 = &S::memfunc3; ============= cut ===================== However, current mainline gives the following error: thales$ ~/gcc-3.4-cvs/install/bin/g++ 6628.cc 6628.cc:2: error: invalid type qualifier for non-member function type 6628.cc:2: error: `const' and `volatile' function specifiers on `fvc' invalid in type declaration regards Christian
next parent reply other threads:[~2003-08-13 18:27 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20020510135600.6628.ge@cs.twsu.edu> 2003-08-13 18:27 ` ehrhardt at mathematik dot uni-ulm dot de [this message] 2003-08-13 18:28 ` ehrhardt at mathematik dot uni-ulm dot de 2003-08-13 19:17 ` pinskia at gcc dot gnu dot org 2003-08-13 19:17 ` pinskia at gcc dot gnu dot org 2003-08-23 15:31 ` pinskia at gcc dot gnu dot org 2004-01-16 3:57 ` giovannibajo at libero dot it 2004-04-02 15:03 ` nathan at gcc dot gnu dot org 2004-04-05 15:54 ` nathan at gcc dot gnu dot org 2004-04-05 15:55 ` nathan at gcc dot gnu dot org 2004-08-05 2:50 ` pinskia at gcc dot gnu dot org 2004-08-05 14:24 ` bangerth at dealii dot org 2005-01-03 21:44 ` pinskia at gcc dot gnu dot org 2005-01-03 21:47 ` austern at apple dot com 2005-01-26 10:27 ` pcarlini at suse dot de 2005-02-22 4:02 ` cvs-commit at gcc dot gnu dot org 2005-02-22 6:27 ` pcarlini at suse dot de
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=20030813182752.6681.qmail@sources.redhat.com \ --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).