Re: Custom destructors -- memory management
On 3 Apr, 07:45, Dave Rahardja
<drahardja_atsign_pobox_dot_...@pobox.com> wrote:
I need to design a container that must hold a set of references to a vari=
ety
of object types, managed by different memory managers. At some time, the
container must destroy each object. Currently I have the following design=
in
mind:
class Destructible // interface
{
public:
virtual void destroy() = 0;
};
class Container
{
public:
// ...
void add(Destructible& item);
// ...
void destroy();
};
void Container::destroy()
{
// ... iterate ...
items[i].destroy();
}
// An item in the container
class Item: virtual public Destructible
{
public:
virtual void destroy();
};
void Item::destroy()
{
MyMemoryManager::Lock lock(this);
~Item();
}
Is there an easier way to do this? Is there a way to make the container w=
ork
with objects without a custom destructor?
Maybe I missed some of the requirements but what's wrong with just
using the normal destructor? If the container uses any of the standard
containers then the destructor will be called automatically. If you
are using pointers then the destructor will be called on delete.
Have you perhaps been using some garbagecollected language like Java
or C# where you don't know when an object is destroyed? Well, in C++
you do, so all you have to worry about is to make sure that the object
is destroyed (going out of scope or using delete on a pointer) and
that the destructor cleans up the stuff that needs to be cleaned up.
--
Erik Wikstr=F6m