Back to General and Gameplay Programming

callback addresses in std::vector

General and Gameplay Programming Programming

Started by floatingwoods February 21, 2011 03:09 PM

7 comments, last by taz0010 13 years, 1 month ago

floatingwoods

364

Author

February 21, 2011 03:09 PM

Hello,

I want to implement a cascading callback mechanism, where I call-back several functions in a row. Those functions should be stored in a std::vector for example (because we don't know how many functions will be registered a-priori).

This is how my callback function looks like:



int callbackFunction(int arg1, int arg2, int arg3, int* arg4, float* arg5)

If the user now provides the callbackRegistration function with above address, how do I set-up things on my side? This is what I have so far, but I am at a loss what type should be inside the std::vector<>:



std::vector<what comes in here?> myCallbackList;



bool registerCallback(int(*callback)(int,int,int,int*,float*))

{

	myCallbackList.push_back(callback);

}

so that later I can simply call in a loop:



for (int i=0;i<myCallbackList.size;i++)

	result=myCallbackList(arg1,arg2,arg3,arg4,arg5);

Thanks for any insight

ApochPiQ

23,138

February 21, 2011 03:14 PM

Have a quick Google for "function pointer typedefs." This will allow you to define a shorthand type name for the function pointer, and easily place the pointers in your vector.

Wielder of the Sacred Wands
[Work - ArenaNet] [Epoch Language] [Scribblings]

rip-off

11,000

February 21, 2011 03:59 PM

bool registerCallback(int(*callback)(int,int,int,int*,float*))[/quote]
If "callback" is the name of the variable, what do you think the type is?
<hr>Consider making your argument list a structure. It will ease maintenance if you decide to extend or change your signature in future. It is also a good idea to include a void pointer to opaque data, which allows for arbitrary state during callbacks. You might even be able to remove some of your parameters if you are including them "just in case".

blog | twitter

SiCrane

11,840

February 21, 2011 04:33 PM

Alternately use boost::function and boost::bind to create callbacks that already store the function arguments.

floatingwoods

364

Author

February 21, 2011 04:38 PM

Thanks to all three of you!

Typedef really simplifies things

Cheers

gazliddon

102

February 21, 2011 04:44 PM

Gah! Too slow

Here's a working program using a typedef



#include <iostream>

#include <vector>



typedef int (*CallbackTypedef)(int arg1, int arg2, int arg3, int* arg4, float* arg5);



std::vector<CallbackTypedef> myCallbackList;



bool registerCallback(CallbackTypedef _callback)

{

        myCallbackList.push_back(_callback);

}





int callBack1(int arg1, int arg2, int arg3, int* arg4, float* arg5)

{

	std::cout << "Hello from callback one!\n";

	return 0;

}



int callBack2(int arg1, int arg2, int arg3, int* arg4, float* arg5)

{

	std::cout << "Hello from callback two!\n";

	return 0;

}



int main(void)

{

	registerCallback(callBack1);

	registerCallback(callBack2);



	int result;

	int arg4;

	float arg5;



	for (int i=0;i<myCallbackList.size();i++)

		result=(*myCallbackList)(0,1,2,&arg4,&arg5);



	return 0;



}

floatingwoods

364

Author

February 22, 2011 01:00 AM

Thanks a lot Gazliddon

Gah! Too slow Here's a working program using a typedef

#include <iostream> #include <vector> typedef int (*CallbackTypedef)(int arg1, int arg2, int arg3, int* arg4, float* arg5); std::vector<CallbackTypedef> myCallbackList; bool registerCallback(CallbackTypedef _callback) { myCallbackList.push_back(_callback); } int callBack1(int arg1, int arg2, int arg3, int* arg4, float* arg5) { std::cout << "Hello from callback one!\n"; return 0; } int callBack2(int arg1, int arg2, int arg3, int* arg4, float* arg5) { std::cout << "Hello from callback two!\n"; return 0; } int main(void) { registerCallback(callBack1); registerCallback(callBack2); int result; int arg4; float arg5; for (int i=0;i<myCallbackList.size();i++) result=(*myCallbackList)(0,1,2,&arg4,&arg5); return 0; }

alvaro

21,604

February 22, 2011 05:52 AM

If you don't want to re-inventing the wheel, a container of callbacks is often called a "signal". What you are trying to implement is probably close to a signal/slot system. Boost has a good library for this.

taz0010

277

February 22, 2011 10:47 AM

boost::function and boost::bind are indispensable if you need actual function objects. "callback" functions cannot operate on class instances in any generic way, so if you ever find yourself needing a vector of function calls, each into an entirely different object and/or method, then boost is your best friend.

callback addresses in std::vector

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

callback addresses in std::vector

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines