I've come across a problem with code similar to this:
/* Foo.h */
class Foo
{
private:
struct Bar {...};
public:
typedef std::vector<Bar> BarList;
};
/* MeepMeep.h */
class MeepMeep
{
public:
void f(const BarList&);
};
When generating wrappers for MeepMeep using Pyste I get access errors because
Pyste expands the BarList typedef to std::vector<Bar>:
struct MeepMeep_Wrapper: MeepMeep
{
void f(const std::vector<Foo::Bar,std::allocator<Foo::Bar> >& p0)
};
I cannot suggest a fix because I am not familiar with Pystes innards. What is
a shame about this defect is that the workaround requires me to violate one
of boost::python's goals of being non-invasive (I must change a private to a
public identifier in target code).
Is Pyste still under active development? I'm not impatient, just curious. If
Pyste is short of active developers I could try to work out a fix for this
<cringes>.
Paul Bridger
