Hi. I am going to prepare relevant code creators for "argument policies".
To be more specific: I am going to work on function_t and
function_wrapper_t code creators. I am going to split those classes to
few classes
function_base_t
function_wrapper_base_t
those classes will contain code that is shared between all derived clas=
sed
user will be able to find all "function" code creators using those clas=
ses
Derived classes will be divided by access type and vitality:
s - static
v - virtual
pv - pure virtual
mem_fun - member function, the short name is taken from C++ std
public:
mem_fun_t
mem_fun_v_t
mem_fun_v_wrapper_t
mem_fun_pv_t
mem_fun_pv_wrapper_t
protected:
mem_fun_protected_t
mem_fun_protected_wrapper_t
mem_fun_protected_v_t
mem_fun_protected_v_wrapper_t
mem_fun_protected_pv_t
mem_fun_protected_pv_wrapper_t
mem_fun_protected_s_t
mem_fun_protected_s_wrapper_t
private:
#developer will be able to override, but not to call
mem_fun_private_v_wrapper_t
mem_fun_private_pv_wrapper_t
free function:
free_function_t
I believe this split will improve readability and maintainability of the co=
de.
Right now it very difficult to add new use case or even to fix a bug.
Now the important thing: if you did not used code creators in your
project - your project
will continue to work.
Thoughts?
--
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/
|
