Member Function Pointers - Typedef vs. Not

In my code I am going to use a typedef for the readability and whatnots, but I like knowing the intricaces of what a type really is, and am wondering why one of these compiles and one does not.

Code:

---

    blooz ( bleez::* r ) ( void ) const [ 4 ] =
    {
        &blaz::doo,
        &blaz::boo,
        &blaz::roo,
        &blaz::koo
    };
   

    typedef blooz ( bleez::*T ) ( void ) const;
    T t [ 4 ] =
    {
        &blaz::doo,
        &blaz::boo,
        &blaz::roo,
        &blaz::koo
    };

---

The first one (non-typedef'd) gives me the errors:

Code:

---

Error        1        error C2090: function returns array

Error        2        error C2440:
    'initializing' : cannot convert from
        'CPoint (__thiscall RotatingPong::CRotatingSquare::* )(void) const' to
        'CPoint *(__thiscall RotatingPong::CRotatingSquare::* )(void) const'

---

Code:

---

    blooz ( bleez::* r ) ( void ) const [ 4 ] =

---

Shouldn't the first one be more like this?

Code:

---

    blooz ( bleez::* r [ 4 ] ) ( void ) const  =

---

A minimal compilable example always helps me come up with a better answer.

Yeah, that's how it should be. I'll try to come up with some of them 'compilable examples' for the future. Many thanks.

try

Code:

---

    blooz ( bleez::* r [ 4 ] ) ( void ) const =

---

ah, they beat me to it

I do that stuff so often. I just leave like 20 windows open, and then remember I was going to reply to something, and then I do only to realize that someone had answered the question like an hour before me. If you watch me closely, you'll see that I delete quite a few posts (That or Ken does. Sorry Ken, my brain is sick).

> but I like knowing the intricaces of what a type really is
I certainly agree for data, but function pointers are special for two reasons.

1. The syntax for declaring them is pretty horrible, especially for more complex cases. Having to repeat that all over the place makes for hard to read and maintain code.

2. There are only ever two things you can do with a function pointer - assign it, or call it.