You just managed to explain to me in less than 15 minutes more than my professor ever succeed to explain to me in 3 hours. Thank you so much! you're awesome
@alef4858 ай бұрын
thank you so much for the video, this channel is going to be a constant visit point on my cs career path
@secondaccount51963 жыл бұрын
This answers 100000 dev people's questions.
@alvarohigino Жыл бұрын
I think I jumped something in my studies, I didn't learn about these different kind of memories and I'm now in memory allocation. 😂
@CodeVault Жыл бұрын
In school (especially in high school) few are taught about these differences. Only later on after students have used it do they learn about it (if ever) I was very confused when my programming teacher told me to use free() on some pointer without explaining anything
@kaamilmirza69633 жыл бұрын
You are a wonderful person
@siddireddyvignesh2 жыл бұрын
Thank you sir for delivering this valuable information Hope u deliver more
@warplanner88522 жыл бұрын
This is because p and q are stack variables pointing to a "clump" of _heap_ memory malloc'ed, right? So that when the function (here, the main() function - hence, the program) goes out of scope, its stack variables are destroyed or dealloc'ed.
@CodeVault2 жыл бұрын
Yes. Those stack variables are deallocated but the malloc-ed clump of memory isn't, thus you get a memory leak
@mccauleybacalla22282 күн бұрын
subscribed thank you so much!
@kevinzebb11 ай бұрын
Caught me off guard, m-alloc?
@CodeVault11 ай бұрын
It comes from "memory allocation"... so, m-alloc seems right to me. Especially since there is calloc which sounds wrong if pronounced as a full word. Pronounce however you'd like
@angel_machariel3 жыл бұрын
This does not work for CodeBlocks, right? It appears this only works in VS. Correct?
@CodeVault3 жыл бұрын
Yes this is only compatible with the Visual C++ compiler. There are alternatives like valgrind for gcc