[pygccxml-development] Argument policies

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

Hi. First of all I created some draft about what functionality is going to =
be
implemented/ignored.  I would like to read your opinion about it.

Also I would like to change the feature name, once again. I prefer
"call wrapper policies".  There are few reasons for this:

1. feature deals with the whole function
2. there are use cases that doesn't deals with argument/return value
3. feature enables to split one function declaration to multiple wrappers

The main idea is to tell the user, that if boost.python call policies deals=
 with
objects/values life time management, call-wrapper policies deals with
code, that
should be generated in order to expose a function.

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