Re: Pointers to Members question

From:

"Victor Bazarov" <v.Abazarov@comAcast.net>

Newsgroups:

comp.lang.c++

Date:

Fri, 21 Sep 2007 16:36:43 -0400

Message-ID:

<fd1a0t$9v6$1@news.datemas.de>

Ben Thomas wrote:

Hi,

Is this code okay and compliant with the standard. As far as I
understand it is correct but I just want to make sure.

Thank you,
Ben.

----

#include <iostream>
using namespace std;

class Base {
public:
  typedef void (Base::*PMethod)(void);
  void Invoke (PMethod p) {(this->*p)();}
};

class Derived : public Base {
public:
  void Method (void) {cout << "Hello World" << endl;}
};

int main (void) {
  Derived x;
  // *** Is the static_cast correct here ? Or could this leads
  // to undefined behavior on some platform / compiler ?
  x.Invoke(static_cast<Base::PMethod>(&Derived::Method));
  return 0;
}

Generally speaking, a member of derived is NOT a member of base,
and that's why the conversion does not exist, and you have to resort
to some tricks (like casts) to silence the compiler that complains
otherwise. The static cast (as I understand it) would be called for
if you have a pointer to member of 'Base' ('Base::*ptr'), somehow
it was converted to a pointer to a member of 'Derived' ('Derived::*')
and then your base wants to call it. Then, since _originally_ the
pointer *was* to a member of 'Base', you're ok to use 'static_cast'.
If the pointer *never was* to a member of 'Base', casting is *not*
the right thing to do. You're correct suspecting that the behaviour
is undefined.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask