function pointer question

I have wracked my brain and cant seem to think of any way to make a container of function pointers. I was wondering if any of you have a solution. I know using virtual functions is better in C++, but that isnt a option at the moment. I would have to do an entire rewrite to do that.

EDIT:
Found a solution on another website using std::vector. I am posting a quick example below

Code:

---

void test()
{
        std::cout << "t\n";
}

int _tmain(int argc, _TCHAR* argv[])
{
        typedef void (*fptr)(void);
        std::vector<fptr> t;
        t.resize(10);
        std::vector<fptr>::iterator it;
        for ( it = t.begin(); it != t.end(); ++it )
        {
                (*it) = &test; //set function pointer to void test()'s address
        }
        for ( it = t.begin(); it != t.end(); ++it )
        {
                (*it)(); //run the function pointed to by t
        }
        system("pause");
        return 0;
}

---

Thank you anyhow, and i hope this helps someone else someday.

Perhaps it would make things easier if you made a typedef.

Code:

---

typedef void (*funcpoint)(int parameter);

---

Then you can use "funcpoint" wherever you'd use int or string, e.g.:

Code:

---

std::vector<funcpoint> v;
funcpoint array[3] = {f1, f2, f3};
void function(funcpoint fp);

---

You can do all of that without the typedef, too -- but the syntax quickly becomes unwieldy.

Hopefully that answers your question. See my vector example above.

A container of function pointers will work, if they are all the same kind of function; viz:

Code:

---

#include <iostream>
#include <vector>

typedef int (*int_ft)(int);
int bob1(int);
int bob2(int);
int bob3(int);
int main()
{
    std::vector<int_ft> func_list;
    func_list.push_back(bob1);
    func_list.push_back(bob2);
    func_list.push_back(bob3);
    int j=4;
    std::cout << func_list[1](j);
    return 0;
}
int bob2(int x) {
    return x*x;
}
int bob1(int x) {
    return x;
}
int bob3(int x) {
    return 1-x;
}

---

If your functions are supposed to take wildly different parameter lists, then things are going to get ugly (but I don't obviously see in that case how any kind of container notation would work).