Printable View
I know alot of languages have this common problem, where you allocate a bit of memory, but it needs to be manualy destroyed. I know that all basicaly allocated memory (int,char,ect) is all deleted at the end of the function or program depending on how you used it.
But I was recently told that it's a good idea to clean up pointers before your program exits, can anyone shead some light on this? Bit confused as it stands
Problem?Quote:
Originally Posted by Blackroot
There's some confusion here. The type has nothing to do with how the thing is allocated. The location of the declaration is all that matters. Variables inside functions are in automatic storage and automatically cleaned up when the containing block is left. Variables outside functions (and outside classes) are in static storage and are cleaned up when the program ends. Stuff allocated with new is in dynamic storage and must be explicitly deallocated.Quote:
I know that all basicaly allocated memory (int,char,ect)
It's a good idea to clean up pointers when you no longer need what they point to. Probably it's the last chance you get. How what you were told relates to this, I have no idea.Quote:
But I was recently told that it's a good idea to clean up pointers before your program exits, can anyone shead some light on this? Bit confused as it stands
Offtopic: I asked the same question (Problem?) recently and got the answer, that modern garbage collection is a lot faster then manual free storage management. I that true?Quote:
Originally Posted by CornedBee
No. It's faster than naive manual free storage management, though. I wouldn't say it's a lot faster.
Whats 'modern garbage collection' and 'manual free storage' ?
Garbage collection.Quote:
Whats 'modern garbage collection' and 'manual free storage' ?
CornedBee meant "manual (free storage management)", not "(manual free storage) management".
Thanks for the clarification, definantly not as bothersome to clean as some languages, luckily.