Re: [pygccxml-development] problem with an array of pointers

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

On Mon, Jul 7, 2008 at 10:28 AM, Gordon Wrigley
<gor...@gm...> wrote:
> Disclaimer: I have no idea what I'm doing and C++ is not one of my strong
> skills. I'm having a problem with py++, boost, msvc and a third party
> library I need to bridge to python. I would greatly appreciate any help I
> can get with this.

:-)

> I don't have the various version information handy but I downloaded all of
> the boost/py++/msvc stuff from the relevant websites last week. After I
> installed everything I made it compile and run the quick start example
> correctly.
>
> I ran the library header through the py++ gui, grabbed the py++ code that
> generated, put it in a .py file, ran that and then copied the resulting
> files into the quick start example.
>
> The header for the library includes this snippet (details obscured to
> protect the guilty):
>
> class bob
> {
> public:
>     double      *fred[4];

This is a bug in Py++.

The code generated for "double* fred[4]" caused the compilation error.
It is not possible to generate code for "fred" without knowing
additional details. In this case Py++ has to exclude this variable
from being exposed and give some warning.

Now, how can you improve the situation:
* exclude variable by your own
* take a look on "return_range" (
http://language-binding.net/pyplusplus/documentation/functions/call_policies.html#return-range
) call policies.

HTH

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