Members - Reputation: 375
Posted 11 December 2012 - 01:17 PM
My understanding is:
1. Use unique_ptr for the pointer that is responsible for managing the object's life.
2. Use shared_ptr for a reference count like system.
If you just want a reference to an object, do you just use a "regular pointer" ?
Members - Reputation: 754
Posted 12 December 2012 - 09:29 PM
1, I use unique_ptr when possible if no need to share ownership. Then I pass raw pointer everywhere. When a function sees a raw pointer, it knows it should not free the pointer.
2, I use shared pointer when I have to share the ownership, but I would avoid it if possible. For shared pointer, I usually pass raw pointer to other functions too, unless the calling function will retain the ownership. Also, if an object doesn't need strong ownership, I use weak pointer when possible. I prefer weak pointer over shared pointer to avoid cycle reference.
3, I rarely use "delete" explicitly thanking to above two rules.
cpgf library -- free C++ open source library for reflection, serialization, script binding, callbacks, and meta data for OpenGL Box2D, SFML and Irrlicht.
v1.5.5 was released. Now supports tween and timeline for ease animation.
Members - Reputation: 241
Posted 15 December 2012 - 03:40 PM
That page has links to unique_ptr, shared_ptr and weak_ptr specific pages as well, all with examples.
Edited by sednihp, 15 December 2012 - 03:40 PM.