[C++-sig] Py++ - problem with split_moduleandreturn_opaque_pointer-policy

[Ganssauge, Gottfried]

> -----Original Message-----
> From: c++-sig-bounces at python.org 
> [mailto:c++-sig-bounces at python.org] On Behalf Of Roman Yakovenko
> Sent: Sunday, September 24, 2006 8:28 PM
> To: Development of Python/C++ integration
> Subject: Re: [C++-sig] Py++ - problem with 
> split_moduleandreturn_opaque_pointer-policy
> 
> On 9/12/06, Roman Yakovenko <roman.yakovenko at gmail.com> wrote:
> > 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.
> 
> Good evening. It took some time, but I finally implemented 
> this functionality.
> Can you check-out  the source code from svn and test it?
Well - I did.
The result still doesn't compile :-(
Do I have to call something in order to trigger your change?
I'm using the test case I sent in original message

Cheers,

Gottfried

> 
> Thanks.
> 
> --
> Roman Yakovenko
> C++ Python language binding
> http://www.language-binding.net/
> _______________________________________________
> C++-sig mailing list
> C++-sig at python.org
> http://mail.python.org/mailman/listinfo/c++-sig
>