whole thing and see if
I can figure out what's going on.
Jim
> Date: Fri, 26 Aug 2011 13:00:11 -0700
> From: tallji...@gmail.com
> To: cplusplus-sig@python.org
> Subject: Re: [C++-sig] Boost Python loss of values
>
> On 08/26/2011 08:27 AM, Jay Riley wrote:
>
Self is indeed a PyObject*
this is a bit confusing
> Date: Fri, 26 Aug 2011 13:00:11 -0700
> From: tallji...@gmail.com
> To: cplusplus-sig@python.org
> Subject: Re: [C++-sig] Boost Python loss of values
>
> On 08/26/2011 08:27 AM, Jay Riley wrote:
> > Hi Jim,
> >
Thu, 25 Aug 2011 13:18:04 -0700
> From: tallji...@gmail.com
> To: cplusplus-sig@python.org
> CC: super24bitso...@hotmail.com
> Subject: Re: [C++-sig] Boost Python loss of values
>
> On 08/25/2011 04:17 AM, Jay Riley wrote:
>
> >
> > And the python exposing is do
member of the base class anyways?
> Date: Thu, 25 Aug 2011 13:18:04 -0700
> From: tallji...@gmail.com
> To: cplusplus-sig@python.org
> CC: super24bitso...@hotmail.com
> Subject: Re: [C++-sig] Boost Python loss of values
>
> On 08/25/2011 04:17 AM, Jay Riley wrote:
>
> >
On 08/25/2011 04:17 AM, Jay Riley wrote:
And the python exposing is done as follows:
class_, bases
>("Attack")
.def("CalculateDamage", &AttackWrapper::CalculateDamageDefault);
This bit looks a little suspect, and I'm surprised that it compiles -
class_ should only take 4 arguments if one
I'm having a really weird issue in boost python. I'm focusing on a particular
property/method to simplify the example. Here's the situation:
In my program, I have a class called Attack. With the following layout
(simplified for example)
class Attack : public Action
{
public:
