Re: [pygccxml-development] Code inserters/Arg policies

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

On 8/6/06, Matthias Baas <ba...@ir...> wrote:
> 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).

I will comment your ideas later. Just wanted to drop another idea to
the existing ones:
Did you use ctypes package? If not, try to find time and to read about it
( http://starship.python.net/crew/theller/ctypes/ ). I think about introducing
fundamental data types to boost.python library or to pyplusplus and
teaching py++ to generate Python code.

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