What is the use of having destructor as private?

by

Basically, any time you want some other class to be responsible for the life cycle of your class’ objects, or you have reason to prevent the destruction of an object, you can make the destructor private.

For instance, if you’re doing some sort of reference counting thing, you can have the object (or manager that has been “friend”ed) responsible for counting the number of references to itself and delete it when the number hits zero. A private dtor would prevent anybody else from deleting it when there were still references to it.

For another instance, what if you have an object that has a manager (or itself) that may destroy it or may decline to destroy it depending on other conditions in the program, such as a database connection being open or a file being written. You could have a “request_delete” method in the class or the manager that will check that condition and it will either delete or decline, and return a status telling you what it did. That’s far more flexible that just calling “delete”.

More Related Contents:

  1. Calling method on an object that is a private member of a class
  2. C++: Life span of temporary arguments?
  3. Dynamically allocating an array of objects
  4. What is the difference between private and protected members of C++ classes?
  5. shared_ptr magic :)
  6. Why do we need a pure virtual destructor in C++?
  7. Object destruction in C++
  8. Is calling destructor manually always a sign of bad design?
  9. calling destructor explicitly
  10. Does C++ call destructors for global and class static variables?
  11. When is a C++ destructor called?
  12. When is an object “out of scope”?
  13. Is it possible to delete a non-new object?
  14. Does delete on a pointer to a subclass call the base class destructor?
  15. Why don’t STL containers have virtual destructors?
  16. Destructor being called twice when being explicitly invoked
  17. Why do we actually need Private or Protected inheritance in C++?
  18. Is a destructor called when an object goes out of scope?
  19. How to access private data members outside the class without making “friend”s? [duplicate]
  20. Why do un-named C++ objects destruct before the scope block ends?
  21. Will exit() or an exception prevent an end-of-scope destructor from being called?
  22. clean C++ granular friend equivalent? (Answer: Attorney-Client Idiom)
  23. Why, really, deleting an incomplete type is undefined behaviour?
  24. Creating an object: with or without `new` [duplicate]
  25. How is it possible (if it is) to implement shared_ptr without requiring polymorphic classes to have virtual destructor?
  26. Why can I access private variables in the copy constructor?
  27. problems with Move constructor and Move overloaded assignment operator?
  28. Lifetime of object is over before destructor is called?
  29. Are destructors run when calling exit()? [duplicate]
  30. Is the whole object freed with a non-virtual destructor and a Base class pointer?

Leave a Comment