The problem is to create a class such that the non-dynamic allocation of object causes compiler error. For example, create a class ‘Test’ with following rules.
The idea is to create a private destructor in the class. When we make a private destructor, the compiler would generate a compiler error for non-dynamically allocated objects because compiler need to remove them from stack segment once they are not in use.
Since compiler is not responsible for deallocation of dynamically allocated objects (programmer should explicitly deallocate them), compiler won’t have any problem with them. To avoid memory leak, we create a friend function destructTest() which can be called by users of class to destroy objects.
Object Created Destroying Object Object Destroyed
If we don’t want to create a friend function, we can also overload delete and delete operators in Test, this way we don’t have to call a specific function to delete dynamically allocated objects.
Please write comments if you find anything incorrect, or you want to share more information about the topic discussed above
- Read/Write Class Objects from/to File in C++
- How to dynamically allocate a 2D array in C?
- C++ Classes and Objects
- Passing and Returning Objects in C++
- When are static objects destroyed?
- How to restrict dynamic allocation of objects in C++?
- Comparing String objects using Relational Operators in C++
- Count the number of objects using Static member function
- C/C++ program to make a simple calculator
- std::any Class in C++
- std:: valarray class in C++
- Array class in C++
- std::string class in C++
- Structure vs class in C++
- C++ String Class and its Applications | Set 2