When the Singleton class is linked, the DLL will get the
Singleton::_instance as an unique static variable.
Well, In my last attempt, it appeared to be like that.
On Fri, Feb 13, 2009 at 5:33 PM, John Reid wrote:
> ZaeX wrote:
>
>> And in my opinion, you'd better be careful if you expect that th
ZaeX wrote:
And in my opinion, you'd better be careful if you expect that the c++
code and python code are using the same singleton instance.
Because there're two Singleton::_instance if you export the Singleton
class to Python. one at c++ side, the other at python side.
I don't think this is
I think reference_existing_object will work.
And in my opinion, you'd better be careful if you expect that the c++ code
and python code are using the same singleton instance.
Because there're two Singleton::_instance if you export the Singleton class
to Python. one at c++ side, the other at python
HI,
The am not sure if which call policy I should be using for this particular use
case,
class Singleton
{
public:
Singleton* create()
{
if(!_instance)
{
_instance = new Singleton();
}
return _instance;
}
static Singleton* _instance;
}
