[pygccxml-development] Code inserters/Arg policies

[Matthias B. <ba...@ir...>]

Hi,

I've just updated the "Code inserters" page in the wiki and added a 
section about non-pure virtual member functions:

https://realityforge.vrsource.org/view/PyPP/CodeInserter#Non_pure_virtual_member_function

The new section examines how the Boost.Python code would have to look 
like to be able to wrap non-pure virtual functions that have a signature 
that is not compatible with Python.

Any comments so far? Are there any use-cases I have forgotten? Are there 
other options how this could be implemented?

The next question (which the text does not deal with yet) is how to 
accomplish this using pyplusplus. The current proposal of a "code 
inserter" API is not able to deal with such things yet (not even with 
pure virtual functions), so this API still needs modifications.
Another question is whether pyplusplus should always create the code 
from option 3 or if the user should be able to specify that some 
use-cases are not important and it is ok that pyplusplus creates the 
simpler code. (So far I would tend to use option 3 in all cases as it is 
the most general option and I don't think it has a noticeable 
performance penalty).

- Matthias-