For example:
struct Vertex
{
int x;
int y;
};
Vertex makeVertex(int xpos, int ypos)
{
Vertex tmp = {xpos, ypos};
return tmp;
}
Would I get a memory leak if I did this?:
Vertex a = makeVertex(30,40);
a = makeVertex(5, 102);
Asked
Active
Viewed 131 times
1
BeeBand
- 10,953
- 19
- 61
- 83
-
7No. You only get memory leaks if you misuse dynamic allocation. – R. Martinho Fernandes Aug 05 '13 at 11:02
-
@R.MartinhoFernandes or with a concurrent access – user2485710 Aug 05 '13 at 11:04
-
You must see [what is a memory leak](http://stackoverflow.com/questions/3373854/what-is-a-memory-leak). – Suvarna Pattayil Aug 05 '13 at 11:04
-
Ok - so no memory leak. Are there any other problems with assigning a POD struct to another POD struct like this? – BeeBand Aug 05 '13 at 11:05
-
@BeeBand No dynamic alloc, no memory leak. – Borgleader Aug 05 '13 at 11:05
-
@beeBand [This link](http://stackoverflow.com/questions/45627/how-do-you-detect-avoid-memory-leaks-in-your-unmanaged-code) isn't exactly relevant but you can use it. – Suvarna Pattayil Aug 05 '13 at 11:10
-
@user2485710 Can you elaborate how you can get a memory leak that doesn't involve misusing dynamic allocation? – R. Martinho Fernandes Aug 05 '13 at 11:11
1 Answers
5
This is perfectly safe.
Memory leaks are caused by (mis)using pointers and memory allocations (typically calls to new that aren't followed by calls to delete, but more complex cases are often where the real problems occur - e.g. not completing the "rule of three (or five)" when dealing with classes that have calls to new).
And of course when using the C style calls to malloc and siblings the code should have a corresponding free call.
Mats Petersson
- 126,704
- 14
- 140
- 227
-
2+1; yes I know the comments also contain an answer but I don't like the practice of answering 'simple' questions in comments on this site. – Bathsheba Aug 05 '13 at 11:15