GUIReader::registerTypeAndCallBack for std::function and add CustomGUIReader for lua

[litefeel]

No description provided.

[litefeel]

[ci rebuild]

[darkdukey]

[ci rebuild]

[litefeel]

[ci rebuild]

[litefeel]

i can build success. why not there?

[minggo]

It seems the error exist in lua-binding.

[litefeel]

@minggo ?

[litefeel]

@minggo i don't know.

[minggo]

The error log is http://115.28.134.83:8000/job/cocos-2dx-pull-request-build/4682/node=android_mac/console.
I will ask somebody to check it.

[minggo]

I have asked @samuele3hu to take a look.

[samuele3hu]

It's a bug of bindings-generator,it didn't consider the value of r in 245 line of tools/bindings-generator/generatory.py.I suggest that skipping the lua bindings for this functions by setting the 'tools/tolua/cocos2dx_studio.ini'.

[minggo]

What did you mean the value of r? Will you please modify tools/tolua/cocos2dx_studio.ini?

[samuele3hu]

En,I will check out this branch and modify it.

[minggo]

@lite3
@samuele3hu fixed lua-binding issue in #7817.

[zilongshanren]

hi @lite3
Why should we change std::map from value to reference?
I think c++11 std::map has move semantic , it won't introduce extra copy performance penalty here.

[litefeel]

@AndyQue

auto map = reader->getParseCallBackMap();

1. this map is copy, reader->_mapParseSelector. can not modify.
2. move semantic used by temporary object. but the temporary map need malloc.

[litefeel]

@minggo the same problem at build failed.
fix it at cocos2d/bindings-generator#131

[samuele3hu]

@lite3 , I check out your branch,and use the latest bindings-generator for cocos2dx_studio.ini, the result is successful.Why did you modify the bindings-generator.

[litefeel]

@samuele3hu

for bindings-generator, I write it at cocos2d/bindings-generator#131

now, i write it again.

old regex: function<(.+) .*\((.*)\)>
now regex: function<(.+) *\((.*)\)>

input string is function<Ref *(void)>
result about first group:
old: Ref
now: Ref *

[litefeel]

@minggo please review

[minggo]

Ok, i have asked @samuele3hu to review lua-binding codes.
Thanks.

[samuele3hu]

@lite3,you are right.If use function<(.+) .*\((.*)\)>,the parse error about ret_type was triggered,through it don't have effect now,thanks.
@minggo , for lua-binding codes,i think it is ok.