Thanks for the suggestions. :-) I put the struct up at the top of the file to keep it global as is more normal. I try to keep the titles shorter because I've found the video performs better that way, and I try to put more details into the description (like in this case I referenced use cases in the description).

@@PortfolioCourses Thanks - I have only heard one other instructor who pronouce char as car - no issue :o) This is of course an educational situation. Is the tendency to have functions not bigger than a screen size and not wider 80 characters to have the code as clear and understandable as possible or?

That's awesome that these videos are helping you! :-)

Thank you Rama! :-)

WOW - thank you very much!!!!!! :-D

Thank you for the kind feedback Idan, and I hope you enjoyed the course! :-)

I'm really glad to hear you think they're awesome, thank you! :-)

It's the same before and after calling free() because free() doesn't modify the memory address that the pointer stores. The function just doesn't do that. All free() does is "make the block of memory that was free'd available again". So when we use malloc() to allocate memory, there is some block of memory that is set aside to be used for our program. Calling free() will make this memory available again, it will no longer be set aside for our program. When we call malloc it returns the memory address for the block of memory that is allocated and we store that into a pointer variable. But free() does not actually modify the value that the pointer variable stores, it ONLY frees the memory AT that memory address. So that's why after calling free() the pointer is the same. And that's why it's a best practice to set a pointer variable to NULL after calling free if we intend to re-use that pointer variable again later, because we are making it clear to the rest of our program that the pointer "points to nothing" which helps prevent us from accidentally using it as if it were pointing to valid memory. :-)

You could do it that way, this video is just for demonstration and learning purposes. In general if we can't allocate memory correctly we would probably do something more than just output an error message, we might exit the program for example. In this video we're just exploring the NULL pointer value. 🙂

That's a great question and yes I think you could do that, but you would want to pass the pointer "by reference" aka "pass by pointer" in order to set the pointer to point to NULL. So something like this maybe... void my_free(int **pointer) { free(*pointer); *pointer = NULL; } .... int *mypointer = malloc(sizeof(int)); free(&mypointer); I'm sure it could be made more general with void but maybe I can make a video on this one day.

@@PortfolioCourses, I think a generalised procedure and a video would be great. Thanks!

@@Mnogojazyk Cool! 🙂

Thank you for the kind feedback. :-)

I hope you enjoyed it! :-)