Re: How does STL map deal with scoping and memory persistance
- From: "Nishant Sivakumar" <nish@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 19 Jul 2005 14:52:22 +0530
You should delete the objects on your own. In general, always 'delete' what
you 'new'.
--
Regards,
Nish [VC++ MVP]
http://www.voidnish.com
http://blog.voidnish.com
"Tommo" <mark.thomson@xxxxxxxxxxxxx> wrote in message
news:1121754302.072833.166840@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Being that I am holding pointers ( that have been new'd elsewhere )
> when i want to remove elements from this map, should i be deleting the
> value under a key or will the container take are of it for me??
>
.
- References:
- How does STL map deal with scoping and memory persistance
- From: Tommo
- Re: How does STL map deal with scoping and memory persistance
- From: Carl Daniel [VC++ MVP]
- Re: How does STL map deal with scoping and memory persistance
- From: Tommo
- How does STL map deal with scoping and memory persistance
- Prev by Date: Re: Whats wrong with this code? (nested classes)
- Next by Date: Re: exporting classes in a DLL
- Previous by thread: Re: How does STL map deal with scoping and memory persistance
- Next by thread: Re: How does STL map deal with scoping and memory persistance
- Index(es):
Relevant Pages
|
