I was trying to fix a bug for the last 3 hours. I tried StackOverflow and all kinds of forums and couldn't find an answer until I watched your video🙌 Thanks a lot !!!!!!!!!!!

Amazing explanation! I have spent literally a week debugging a code, with googling and many articles StackOverflow etc. Usually big vague paragraphs, and no answer at the end! and here, the author right away clearly points out that you have to allocate memory for struct members as well and use strcpy. Thank you!

Outstanding presentation as always! I'd like to suggest an enhancement to further streamline the management of dynamic memory, especially considering the complexities introduced by structures containing pointers to such memory. Adopting a systematic approach, akin to what one might find in object-oriented languages, by implementing functions that act as creators, modifiers, and destructors for your data structures, can be quite beneficial. Creation: A function to dynamically allocate an array of points. Modification: A function to adjust the size of this array, ensuring efficient memory use. Destruction: A function to properly free the allocated memory, preventing leaks. These concepts encapsulate the complexities of direct memory management, making your code more organized and easier to maintain. This approach is particularly helpful for those transitioning from higher-level, feature-rich languages to C, offering a familiar paradigm to new C programmers. Moreover, it's beneficial to constantly ask yourself, "How would this be handled in a more advanced language?" and then aim to manually implement your version of that solution in C, or find a library that can help. This mindset not only encourages the development of robust, maintainable, and efficient code but also deepens your understanding of what these more advanced languages are doing for you in the background. Understanding these underlying mechanisms can make you a more knowledgeable and versatile programmer, as it provides you with insights into both the high-level abstractions and the low-level implementations that make modern computing possible.

Your videos are such lifesavers -- thank you!

one time explained, onetime understood. Thank you a lot

This is great, I found exactly what I was looking for

Great video! Thank you so much, it helped a lot! Was having a hard time figuring out what needs to be used to assign my string value to char* property in struct. For some reason array[2].description = "string" overwrote the description property for array[0] and array[1] as well, with the same value. Stackoverflow and other forums didn't help, you did.. it's the strcpy that is needed here!

Your video is the answer to all my questions, thank you

Such a good video, soooooooo much info!

Thank you Kevin, that was helpful.

Thanks for your helpful tutorial video.

Kevin; these are great videos. Just a question about freeing memory; is it possible to declare the size of the memory for the description variable inside the struct definition. In this way the free() function would only have to be called once when freeing the memory for any Point variable.

very nice. simple and useful.

Thaks!

Thank you!

Hi sir one question here we can use -> operator there also like (array+2)->y=3; can you pls reply to me whether it's right or wrong....

Hi, i have a question: while allocating memory, i saw lots of people doing this (int*)malloc(...) is it necessary or just nice to have. Does it cause any issues? Thank you.

where did you learn how to program in C so well? Also thoughts on CPP?

I've been designing embedded systems for 35 years now, and I've never had to use dynamic memory, or floating point datatypes. I'm curious if anyone else had the same experience? I've been on a few architecture design reviews where I've had some pushback, but we ended up without needing malloc.

esta genial el video

What happens if they wrote like this Point *array[100] is it means without malloc is it allocates space by itself what is it means. My prof wrotes like that

Insane

Hey there, what IDE is that?

Well done, you deserve to grow in subscripsions and I'm learning a lot. I'm actually not using an array when dealing with allocated structs yet. It may be a wrong approch, but I find it easier to use an extra pointer to manipulate the allocated memory and move the size of the struct. What do you think? int num = 2; point *mem = malloc(sizeof(point) * num); point *p1 = mem; p1->x = 3; p1->y = 2; p1++; p1->x = 6; p1->y = 1; p1--; int i = 0; while (i++ < num) { printf("%d, %d ", p1->x, p1->y); p1++; } free(mem);

👍👍👍

Thank you for your Vide. I am having trouble with malloc when I put the following linse: Point *p2; p2 = malloc(sizeof(Point)); I get the error : Severity Code Description Project File Line Suppression State Error (active) E0513 a value of type "void *" cannot be assigned to an entity of type "Point *" StructSub C:\Users\mvj32\source epos\StructSub\StructSub\Source.cpp 21 lude #include typedef struct { int x; int y; } Point; int main() { Point p1; p1.x = 4; p1.y = 5; printf("(%d, %d) ", p1.x, p1.y); Point *p2; p2 = malloc(sizeof(Point)); return 0; }

Amazing explanation! I have spent literally a week debugging a code, with googling and many articles StackOverflow etc. Usually big vague paragraphs, and no answer at the end! and here, the author right away clearly points out that you have to allocate memory for struct members as well and use strcpy. Thank you!