clear() before delete? --hash_map

[newbie]

For STL containers like hash_map, need I explicitly call clear()
before delete()ing it?

e.g.
hash_map<string, MyClass*> *my_map;

my_map = new (hash_map<string, MyClass*>);

....
....

end(); ++it)

delete it->second;
// do I need call my_map->clear()?
delete my_map;

Thank,

 

[Mark P]

For STL containers like hash_map, need I explicitly call clear()
before delete()ing it?

hash_map is, AFAIK, not yet standard. Nonetheless the answer to your
question is "no".

 

[red floyd]

For STL containers like hash_map, need I explicitly call clear()
before delete()ing it?

e.g.
hash_map<string, MyClass*> *my_map;

my_map = new (hash_map<string, MyClass*>);

[redacted]

delete my_map;

Any particular reason you're new-ing this, instead of declaring it:

hash_map<string, MyClass*> my_map;

In general, you don't need to use new and delete as often as most people
seem to think.

 

[newbie]

For STL containers like hash_map, need I explicitly call clear()
before delete()ing it?

e.g.
hash_map<string, MyClass*> *my_map;

my_map = new (hash_map<string, MyClass*>);

[redacted]

delete my_map;

Any particular reason you're new-ing this, instead of declaring it:

hash_map<string, MyClass*> my_map;

In general, you don't need to use new and delete as often as most people
seem to think.

does hash_map<string, MyClass*> my_map; (which I am not sure how many
byte it needs)
use more memory on stack, suppose the class is initialized as a stack
variable,
than "hash_map<string, MyClass*> *my_map;" (which is just a pointer)?

Thanks,

 

[James Kanze]

does hash_map<string, MyClass*> my_map; (which I am not sure how many
byte it needs)
use more memory on stack, suppose the class is initialized as a stack
variable,
than "hash_map<string, MyClass*> *my_map;" (which is just a pointer)?

Maybe, but not enough to matter.