On 30 Jan 2012 at 1:21, Davidson, Josh wrote:
> Similar behavior, but now the storage import is FUBAR. Does anyone
> understand what is going on here?
>
> I'm using x64 Python 2.6.6 on x64 RHEL 6. Gcc version 4.4.6.
It's never popular for me to say this, but shared libraries really
aren't im
Hi all
I can't seem to figure out how to wrap this in Boost.Python without the
need for auxiliary functions:
#include
#include
using std::string;
using namespace boost::python;
class A
{
string m_s;
public:
A(string const& s) : m_s(s) {}
// read-only access (
string const& s() const
On 01/30/2012 09:32 AM, Michael Wild wrote:
Hi all
I can't seem to figure out how to wrap this in Boost.Python without the
need for auxiliary functions:
string& s() { return m_s; }
The second argument to add_property should be an actual setter, not a
non-const-reference getter. In
On 01/30/2012 04:58 PM, Jim Bosch wrote:
> On 01/30/2012 09:32 AM, Michael Wild wrote:
>> Hi all
>>
>> I can't seem to figure out how to wrap this in Boost.Python without the
>> need for auxiliary functions:
>>
>
>
>
>>string& s() { return m_s; }
>
> The second argument to add_property sho
On 01/30/2012 12:11 PM, Michael Wild wrote:
That's what I've been referring to as "auxiliary" functions. If
possible, I'd like to avoid them because I don't fancy writing hundreds
of those... I could live with calling a template. However, so far I
haven't been able to come up with one that is suf
On 01/30/2012 07:28 PM, Jim Bosch wrote:
> On 01/30/2012 12:11 PM, Michael Wild wrote:
>> That's what I've been referring to as "auxiliary" functions. If
>> possible, I'd like to avoid them because I don't fancy writing hundreds
>> of those... I could live with calling a template. However, so far I
