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 side.
2009/2/13 Balasubramanyam, Shivakumar <sbala...@qualcomm.com>
> 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;
> }
>
> // Initialization
> Singleton* _instance=NULL;
>
> Is return_value_policy<reference_existing_object> the right call policy to
> use?
>
>
> Thanks,
> Shiva
>
> _______________________________________________
> Cplusplus-sig mailing list
> Cplusplus-sig@python.org
> http://mail.python.org/mailman/listinfo/cplusplus-sig
>
--
Time is mana, we must hurry
_______________________________________________
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinfo/cplusplus-sig
