Thomas Fjellstrom
Thomas Fjellstrom
It looks like no, as is it isn't supported. The magic C++ template magic is not able to detect default arguments. I'm not actually sure how to support variable number...
Yes, we do know how many items are in the stack when our internal call method is called, the main problem is when storing function pointers, they store ALL of...
The fancy tuple unwrapping code may not like only doing partial unwrapping. And we'd open a larger hole where it'd happily pass too few arguments to functions.
It's possible we can add a parameter to the method() function to pass the minimum number (X) of parameters, and LuaGlue can allow sending X or more parameters. It would...
That's what I meant. Always pass the parameters.. It's annoying, but it might be the only solution. I don't know of a good way to handle optional parameters. Even my...
I will at some point attempt to get it to work. I'm keeping it on my todo for now.
Hm that's not a bad idea. It would cut down on the number of stack specializations. Though I'm not sure that is valid for both 32bit and 64bit targets. signedness...
Lamda wise, you can pass them into a std::function and pass that around no? (not that I wont add lambda support, but it is a work around)
That's ok. I'll see about adding lambda support . As for your setRect example, that's a bit more interesting. I haven't added passing table's back to c++ yet. But your...
It seems std::function support in `g.invokeFunction` is broken at the moment. I'm working on a fix. And it may allow binding to lamdas.. but internally it'll turn things into std::function's...