Re: [pygccxml-development] Feature proposal: "Argument policies"

[Roman Y. <rom...@gm...>]

Okay lets see if I understand you right.

class wrapper{

return_type function( arguments ) <=3D=3D here user can modify function sig=
nature

    variables <=3D=3D here user declares few variables and can bind them
with arguments
                          and/or return value

    make "native" call ( mix of variables and arguments ) <=3D=3D here I
think he should
                         be able to bind return argument to some variable

    construct return value  <=3D=3D here user can check result of "native" =
call and
                         throw exception or construct return value.

}

Now, the communication between steps done using function_wrapper_t
code creator ( =3D=3D wrapper_manager  ).
To be more precision: using variables and arguments collections.

I think, I've got you right.

If so, what interface you give to the user? Direct access to the code creat=
or?
I am not talking about wm.declare_local( ... ), as for me this is too
low-level.

Comments?

P.S.
Small comment about clean_up( :-) ) state.
In C++ developers can use RIIA technique. So I think, that clean up
state is nessecary. I don't want to force developers to use it, but I
also don't want to
provide "too mach" help with hand written clean up actions.


--
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/