No, I compiled boost.python with just ' --with-python '.
and I just made a last try to change the 'shared_ptr const& ' to
'shared_ptr&',
and things suddenly become right. ^_^
well I don't quite understand what's going on inside though. maybe
'shared_ptr const&' made temp copy (?)
on Thu Mar 12 2009, ZaeX wrote:
> I just built the boost.python 1.36 with Python2.6.1 and tried again, and it
> still turned out to be 0x in debug build.
Have you read
http://www.boost.org/doc/libs/1_38_0/libs/python/doc/building.html#python-debugging-builds
?
--
Dave Abrahams
BoostPr
on Wed Mar 11 2009, Haoyu Bai wrote:
> Hi,
>
> I have posted this to Boost development mailling list before and many
> people suggested me to repost here, so I did.
>
> I'm a student who has finished SWIG's Python 3.0 support in GSoC 2008.
> I'd like to contribute my knowledge of Python 3 migrat
I just built the boost.python 1.36 with Python2.6.1 and tried again, and it
still turned out to be 0x in debug build.
And I made sure this is not caused by 'a = B(a)'-like typo.
Maybe it's something concerning the project setting or something went wrong
with my compiler(?)
Whatever, I thin
on Thu Mar 12 2009, athor wrote:
> * You don't *need* a const& to break cyclic reference. Passing a shared_ptr
> by value works too.
And that's almost always a better idea. If you *do* have a reference
cycle, consider weak_ptr instead.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.
zaexage wrote:
>
> I got a 'class Manager' which contains a std::set of shared_ptr;
> and 'class Entity' has a auto_ptr as member
> and 'class StateMachine' needs shared_ptr as member variable to
> access some functions outside.
>
> So, in order to break cyclic reference, I make the StateM
Hi,
I copied the code and tried again, and find out that this 0x
problem would still occur at debug build,
and when I switched to Release build, the 'b.ShowPtr()' gave a wrong
address.
But since this code is correct at your side, I think it's possibly because
the precompiled boost.python
On Thu, Mar 12, 2009 at 4:50 AM, Niall Douglas
wrote:
> On 11 Mar 2009 at 13:42, Ravi wrote:
>
>> On Wednesday 11 March 2009 12:38:55 Haoyu Bai wrote:
>> > > 1. Thread safety
>> > > 2. PyFinalize support
>> > > 3. Easier methods to write to_python/from_python converters
>> > > 4. Python 3.0 suppor
Hi,
I just tried your example and could not reproduce the "feature". I made a
few minor modifications like fixing typos and adding a cout statement in the
constructor of A but nothing that should affect the result.
A few things that could cause you problems:
* Passing shared_ptr by reference and
On Thu, Mar 12, 2009 at 2:30 AM, troy d. straszheim wrote:
> 1. What are the responsibilities of the mentor(s)?
>
I took a loot at GSoC FAQ [1] but indeed there's no specifically
requirement for mentor. I think a mentor is who in charge of to help
the student to find out solution for problems, s
Thanks Roman,
I think I will take the advice to try working around this problem.
On Thu, Mar 12, 2009 at 1:17 PM, Roman Yakovenko
wrote:
> 2009/3/11 ZaeX :
> > Hi,Roman:
> >
> > I have tried adding call policy on my constructor, but I'm really no good
> at
> > this.
> > I have tried all the combi
11 matches
Mail list logo
