I have read from the Qt documentations about QPointer, QSharedPointer and QWeakPointer classes. It says:
QPointeris a template class that provides guarded pointers to Qt objects and behaves like a normal C++ pointer except that it is automatically set to 0 when the referenced object is destroyed and no "dangling pointers" are produced.QSharedPointerclass holds a strong reference to a shared pointer.QWeakPointerclass holds a weak reference to a shared pointer.
My questions is "What is the difference between these classes?". i.e what is the difference between a pointer to an object and a reference to a pointer? Are they all pointers to objects with different mechanisms and behaviors?
QPointer:
QPointercan only point toQObjectinstances. It will be automatically set tonullptrif the pointed to object is destroyed. It is a weak pointer specialized forQObject.Consider this fragment:
QSharedPointer
A reference-counted pointer. The actual object will only be deleted, when all shared pointers are destroyed. Equivalent to
std::shared_ptr.Note that as long as there is a shared pointer, the object is not deleted!
QWeakPointer:
Can hold a weak reference to a shared pointer. It will not prevent the object from being destroyed, and is simply reset. Equivalent to
std::weak_ptr, wherelockis equivalent totoStrongRef.This can be used if you need access to an object that is controlled by another module.
To use a weak pointer, you must convert it to a
QSharedPointer. You should never base a decision on the weak pointer being valid. You can only usedata()orisNull()to determine that the pointer is null.Generally, to use a weak pointer, you must convert it to a shared pointer since such an operation ensures that the object will survive for as long as you are using it. This is equivalent to "locking" the object for access and is the only correct way of using the object pointed to by a weak pointer.
QScopedPointer:
This is just a helper class that will delete the referenced object when the pointer goes out of scope. Thus, binds a dynamically allocated object to a variable scope.
You can use this for RAII semantics for locals, e.g.:
The item will also be deleted in case of an exception
Another use case can be member variables of an object. Then you don't need to write a destructor for those: