[C++-sig] Py++ - problem with split_module andreturn_opaque_pointer-policy

[Roman Yakovenko]

On 9/12/06, Ganssauge, Gottfried <Gottfried.Ganssauge at haufe.de> wrote:
> What do you think about a code generator more "knowledgeable" about
> return_value_policy?
> One that could see "hey, I'm being ordered to return_opaque_pointer" and
> then would call that macro wherever neccessary?
> In the code generator it could go like:
>   if calling_policy is return_value_policy(return_opaque_pointer):
>     opaque_base = remove_pointer (current_decl.return_value.type)
>     add_declaration_code ('BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID(%s)'
> % opaque_base)

This is even better solution. I will implement it and will let you know.

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