Printable View
Suppose I have a function in the code of which I havefurther down I append elements to myvectorCode:
like this
Where does the allocation take place? On the stack? On the heap?Code:
What do I need to know about freeing the memory?
The QVector object is on the stack (where you allocated memory for it) but he <most likely> allocates memory on the heap for the elements (and take care to release it), if you need to know more you can open the source code and see exactly how this works.
The QVector will take care of the memory, you don't need to worry, it will not leak.
I believe that allocation for both will take place on the heap. For variables where you do not specifically allocate memory withQuote:
Originally Posted by feraudyh
the "new" operator, temporary space is allocated for them on the stack. This means that all allocation and deletion will be handled
for you, but it also limits the scope of those variables to that function on the stack where they are defined. Hence, every time you
jump to a different part of the stack (usually through a different function call) if you can only send through values as parameters, not
variables that can be modified. This method of scope and how memory allocation works is perhaps the most important thing to understand
about c, and one of the more important things to understand in c++.
Just for clarification: when I said "both" i mean the "QVector" and the "int" with a value of 3 that you place into the vector.
@SneakyPeterson: The QVector object is allocated on the stack and it has some pointers to typename T, witch (the pointer itself) it's also on stack, but it is used to allocate memory on the heap.
If the vector itself will be on the heap, how it will be auto-deleted? It can't, it doesn't have the "parenting thing" (only the GUI parts on Qt have that).
I wasn't aware that QVector worked that way with primitives... Ah well.
http://blogs.pitch.com/plog/the_more_you_know2.jpg