public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "René Møller Fonseca" <fonseca@mip.sdu.dk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8271: Templates and pointers to const member functions
Date: Tue, 07 Jan 2003 19:26:00 -0000	[thread overview]
Message-ID: <20030107192601.16837.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2203 bytes --]

The following reply was made to PR c++/8271; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Ren=E9_M=F8ller_Fonseca?= <fonseca@mip.sdu.dk>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	bangerth@ticam.utexas.edu, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/8271: Templates and pointers to const member functions
Date: Tue, 07 Jan 2003 20:18:51 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8271
 
 Hi,
 
 It is GCC that is wrong. The qualifiers are part of the type and must not be ignored. Here is a more elaborate implementation.
 
 >>>>>>
 #include <iostream>
 
 using namespace std;
 
 class MyClass {
 public:
   void mutableMethod() throw() {
     cout << __func__ << endl;
   }
   void constMethod() const throw() {
     cout << __func__ << endl;
   }
   void volatileMethod() volatile throw() {
     cout << __func__ << endl;
   }
   void constVolatileMethod() const volatile throw() {
     cout << __func__ << endl;
   }
 };
 
 MyClass* o = new MyClass();
 
 template<class CLASS>
 void mFunction(void (CLASS::* method)()) {
   (o->*method)();
 }
 
 template<class CLASS>
 void cFunction(void (CLASS::* method)() const) {
   (o->*method)();
 }
 
 template<class CLASS>
 void vFunction(void (CLASS::* method)() volatile) {
   (o->*method)();
 }
 
 template<class CLASS>
 void cvFunction(void (CLASS::* method)() const volatile) {
   (o->*method)();
 }
 
 int main() {
   // cFunction(&MyClass::mutablemethod); // ERROR
   cFunction(&MyClass::constMethod); // OK
   mFunction(&MyClass::mutableMethod); // OK
   mFunction(&MyClass::constMethod); // ERROR - GCC bug
   // vFunction(&MyClass::volatileMethod); // ERROR
   vFunction(&MyClass::volatileMethod); // OK
   mFunction(&MyClass::constVolatileMethod); // ERROR - GCC bug
   cFunction(&MyClass::constVolatileMethod); // ERROR - GCC bug
   vFunction(&MyClass::constVolatileMethod); // ERROR - GCC bug
   cvFunction(&MyClass::constVolatileMethod); // OK
   return 0;
 }
 <<<<
 
 The generated output (using GCC-3.2):
 constMethod
 mutableMethod
 constMethod
 volatileMethod
 constVolatileMethod
 constVolatileMethod
 constVolatileMethod
 constVolatileMethod
 
 cheers,
 René
 


             reply	other threads:[~2003-01-07 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 19:26 René Møller Fonseca [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07 20:05 bangerth
2002-10-17 15:26 bangerth

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=20030107192601.16837.qmail@sources.redhat.com \
    --to=fonseca@mip.sdu.dk \
    --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: link
Be 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).