• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Servant of the Lord

std::function, and callbacks, and functors, oh my!

2 posts in this topic

I've used callback functions alot before, and I understand what a functor is, but I've never created a function that takes a functor as a parameter.

If I go like this:
[code]typedef bool (*CallbackFunc)(int); //Typedefining a function pointer returning a bool and taking one int parameter (right?).
void DoSomething(CallbackFunc callback);[/code]

That won't accept functors. So what is the best way to accept functors OR functions?
Looking at how the standard library does it, I see they use templates, which makes sense.
[code]template <class funcType>
void DoSomething(funcType callback);[/code]

That, because it is a templated parameter, accepts both functors and functions.
Nice... but is there a better way? What if I have a function that takes more than one callback:
[code]//Two callbacks:
template <class funcTypeA, class funcTypeB>
void DoSomething(funcTypeA callbackA, funcTypeB callbackB);

//Three callbacks:
template <class funcTypeA, class funcTypeB, class funcTypeC>
void DoSomething(funcTypeA callbackA, funcTypeB callbackB, funcTypeC callbackC);[/code]

I'm not really liking that too much. I just read up on std::function() (C++11) and am trying to understand it.
Can it really accept functions or functors (or lambdas)?

How does this work in practice?
[code]typedef std::function<bool(int)> CallbackFunc;

//template <class funcType>... Template not needed?
void DoSomething(CallbackFunc callbackA, CallbackFunc callbackB, CallbackFunc callbackC);[/code]

Is that the proper usage? Am I understanding it correctly?
And I can pass one function to say, the first parameter, and two different classes as functors to the second and third parameter?
[code]class FunctorA;
FunctorA functorA;

class DifferentFunctorB;
DifferentFunctorB differentFunctorB;

bool myFunction(int value);

DoSomething(myFunction, functorA, differentFunctorB);[/code]

This is valid? Without DoSomething() itself being templated? With only one typedef of CallbackFunc taking just the return type and the parameters?

Share this post

Link to post
Share on other sites
[quote name='Servant of the Lord' timestamp='1348024985' post='4981522'][list=1]
[*]Can it really accept functions or functors (or lambdas)?
[*]How does this work in practice? Is Template not needed?
[*]And I can pass one function to say, the first parameter, and two different classes as functors to the second and third parameter?
[*]The compiler emits some code mapping lambda to [font=courier new,courier,monospace]std::function[/font]. How it happens, it's unclear to me as lambda is some really odd type. It will map correctly even when using capture lists (which isn't completely unexpected after all). It's important to note those are in fact unrelated types and not just "functions", there will be casts. I'm not quite sure how it's going to work with plain functions, but I suppose it's going to work (see [font=courier new,courier,monospace][url="http://www.gamedev.net/blog/32/entry-2254352-the-new-c-functions/"]void handler(EventArgs const&)[/url][/font] in the first code box or [font=courier new,courier,monospace][url="http://www.gamedev.net/blog/32/entry-2254352-the-new-c-functions/"]void HandleMouseClick[/url][/font], to the end of the page).
[*]I see no problem. No, there's no need to use [font=courier new,courier,monospace]template[/font].
[*]I'm not sure myself but I think as long as [font=courier new,courier,monospace]operator()[/font] is correctly overloaded, it will work.
[/list] Edited by Krohm

Share this post

Link to post
Share on other sites
std::function (or boost::function if C++11 is not available) would indeed be the way to go. Templates are the preferred way, if they are not possible use std/boost::function. The alternative would be handrolling something by yourself. However, unless you have some interesting domain specific restrictions you would be just implementing std/boost::function.

For the record, I have not looked at the code of std/boost::function but I would guess the implementation is as expected: the function object is a facade which contains a pointer to a base class with a pure virtual function to call. The concrete instance created is decided based on the template parameter passed to the std/boost::function constructor. Template magic and/or SFINAE might be required to differentiate all important types. The variable number of arguments might need a lot of black magic depending on your compiler as well. More black magic might be used to avoid a call to new.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0