my thotsa static member is a class member, while a non-static member is an boject member. It is hard for the compiler to check validity of the sytax if the member fuction poiter is an object memeber. because the compiler cannot always know the exact memeber function it is pointing to at compile time.

followon questionThanks, VeryGood. The compiler really complains about non-static member functions as shown in error message. My followon question is that: in a class defintion, there are acutally many non-static member function. Here the member function is private, does it matter? Is it possible to define a non-static private member function? TIA

It seems that you are confused...1) The sample you gave above is NOT a declaration of member function. Instead, the typdef statement simply aliases a data type of member function pointer as "Omf" for the ease of reference. 2) No matter farray is declared as static or not, the syntax is acceptable! That is, there is NO compelling reason that farray must be declared static. Please double check.

It seems that you are confused...1) The sample you gave above is NOT a declaration of member function. Instead, the typdef statement simply aliases a data type of member function pointer as "Omf" for the ease of reference. 2) No matter farray is declared as static or not, the syntax is acceptable! That is, there is NO compelling reason that farray must be declared static. Please double check.

1-yes, 2-noI agree with your first point. It is really just aliasing. I had mis-used some words such as static functions. It is not private function. farray is a pointer to array of functions. farray is a private member of class Object. So the problem is that the keyword static is not allowed to be omitted, otherwise compiler complains as shown in the error message [quote] menu1.cpp:17: 'void (Object::* Object::farray[3]()' is not a static member of 'class Object' [/quote] So you see the problem?

I saw your problem. But I don't think that's thepoint. I compiled the following code using g++ version 2.95.2 on Solaris: class Object { private: typedef void (Object::*Omf)(); /*static*/ Omf farray[3]; }; Compilation gave no error. I suppose the error was caused by other factors.

my thotsa static member is a class member, while a non-static member is an boject member. It is hard for the compiler to check validity of the sytax if the member fuction poiter is an object memeber. because the compiler cannot always know the exact memeber function it is pointing to at compile time.

Other source of error?Flying, i investigate it again. I think the problem may caused by the initialization of farray. In the public part, i defined some public functions, and i initialize the farray with these public functions. Class Object { public: void retrieve() {...} void insert() {...} void update() {...} private: typedef void (Object::*Omf)(); Omf farray[3]; }; Object::Omf Object::farray[3]= { &Object::retrieve, &Object::insert, &Object::update }; &Object::retrieve and such are fixed addresses, so farray must be defined as static, correct? Is this a rule defining a static member? What are the rules for definition of static members? TIA

only a static member can be initialize in this wayyou should initialized it in you constructor instead.