Re: [pygccxml-development] Error after updating pyplusplus...

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

On 4/27/06, Matthias Baas <ba...@ir...> wrote:
> Hi,
>
> the latest version of pyplusplus now turns a member variable like
> "float* depthArr" into a property which won't compile. During
> compilation you get a weird error from Boost that's pretty much useless.
> For now, I don't need those variables so I just ignore them explicitly
> now and everything is fine again.
> But I just thought I mention it here anyway as in my opinion, pyplusplus
> should never generate code that won't compile.

You are right. My opinion is: pyplusplus should generate code that
actually works.
If it can do it - skip it.

The problem you are talking about. Recently there were few mails about how =
to
expose member variable pointers. I implemented solution for this. Obviously
I did not take into account some use cases. ( pointer to fundamental
type I think )

So, thank you for your input. I will fix it next week.


> - Matthias -

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