Top Comments
Video Responses
All Comments (20)
-
Visual Studio sucks. Other than that, good tutorials!
-
Malloc calls HeapAlloc HeapFree or whatever system calls are platform dependant for memory management by default. Because Malloc is standard c library not platform dependant so it's implementation varies depending on which platform/architecture you're running on. Only advantage to using system calls is when you get into low-level programming and you want processes to share memory for ipc mostly on linux though because on windows you're better off using threads
-
From this point I think he got bored of doing tutorials and began explaining very fast without much clarification hehe!
-
Thank you, I got this now!
-
I didnt understand this tutorial well, in my point of view, allocating memory is something like changing his value but isnt easier just doing something like "MyVariable = MyValue" instead of alocating it on the memory and changing it there?
Sry, im spanish speaker so my english listening isnt good so it is had for me to understand his explanation.
-
A bit too fast, some points could have been explained in more detail.
-
Dynamic memory is what I always get hung up on. Thanks for doing this.
-
Dude i was so stuck at trying to understand this in class, now i understand it soo much better, thank you for taking the time to put this tutorial up :)
-
i think this kind of lesson should be put at the end of all of his c++ vid.. because this is not necessary i think.. although this is useful but this makes some beginners confuse to learn.. btw really love the lesson
-
To answer some questions: "malloc" and "free" are for memory allocation in C. "new" and "delete" are for C++. Internally, "new" calls "malloc" and then calls the object's constructor. "delete", likewise, calls the object's destructor and then frees the memory. HeapAlloc and HeapFree are advanced forms of memory management for Win32 which are unnecessary for anyone watching a tutorial lesson. Just use "new" and "delete".



Finally, good C++ tutorials. All others suck and show messy and inefficient code. FINALLY! XoAX, I believe the new keyword leads back to malloc. For C++ this is perfectly fine, however, if you are using Win32 along, I believe you should utilize HeapAlloc, HeapFree and so on.
AES256bit 2 years ago 11
Great lesson !
MaxRoudriges 1 year ago 6