Local vs global variables in C 

Thanks man. We're all alright! I'm still active on the Discord server. More videos are coming soon!

Thanks! All the playlists on the channel are based on topic and as close as possible to a proper order. The videos weren't made with an order in mind so I just ordered them from the easiest to hardest.

Interesting topic, I noted it down!

I will keep that in mind. I might upload some videos on Java

I'll look into the different compilers, I think it's a great topic for a video! You can always search it on our website: code-vault.net Here's the video: code-vault.net/lesson/wkec83yooo:1603733527208

It's not that tricky. sleep you call when you want your thread/process to stop its execution for some time. And wait() you call when you want to stop a processes execution until another child process finishes its execution. So they are very different functions

It's on my todo list. I will get to it whenever I have time

I will get back to it soon! Be on the lookout!

I briefly talk about calloc in this video: code-vault.net/lesson/akvjz24gn5:1603733521718

I noted it down

It's not quite like that. Your first point is mostly correct but they both use the same amount of memory (if they are the same type of course), it's just that local variables can be deallocated in the middle of running the process, thus freeing up some memory for the process to use. Local variables sometimes can decrease efficiency, although it is such a small decrease it's not worth thinking about. It usually just involves increasing or decreasing the stack pointer value which is super quick, only the compiler might do a bit more work to figure out how much memory it needs to allocate for the stack of a specific function call (but this doesn't affect runtime performance).

@@CodeVault thanks for your answer! This memory/efficiency thing became very interesting to me since I started coding games which includes Game Loop usage. So, if there is a piece of code in the loop with some method that has a local variable initialization line, plus some extra methods that assign same values to that variable (like getting length or dimention etc.)... well, what happens is that loops iterate hundreds of thousand or even more times per second, all those local variable keep on getting created and destructed hundred of thousand times per second... But if I just get one global variable outside the loop and assign it value just once. Well, I guess I need to write some code to test it all 😄

The local variable's memory is allocated and deallocated only once (even if it is a loop). Of course, the assignment will be done multiple times if it's in a loop. I have to check if for objects in C++ the same applies for constructing and destructing the data. I assume those get called each iteration of the loop

Yes, I am still replying to comments

@@CodeVault thank you

I'll look into it!

In this video I explain them: code-vault.net/lesson/dbijqbwu2a:1603733526118

Hmm, to solve this issue you have 2 options: 1) Check if eof was reached in the file (feof(inputFile)) and don't remove the last character in that case 2) The easiest solution would be to just add a after the last line inside the input file. That's what I usually do to make all the lines be exactly the same.

Well, kinda late, but you could check if the current char is and the next one is \0 using a for. If that condition checks, replace the current char with \0

It's quite complex. You could either use the native APIs for GUIs (like Win32) or a library with cross platform compatibility like GTK+

@@CodeVault thanks so much sir lots of love ❤️ from India. Also I have one question ..can we add audio file in c program..& how

@@CodeVault plz upload one graphics program video..I have installed GUI library files but I don't know how to linked library files with visual studio code

I'll look into it

In most Object Oriented languages, you can argue that global variables are bad practice but, in C, it's sometimes a necessity. The main problem with global variables is they can be modified from wherever in your code and it could cause unexpected issues. A lot of the time is better to return a new value (struct or primitive) from a function you're calling so that, instead of working with a global variable, you use the returned value instead (and that value can't changed outside of the scope of that function, unless you explicitly let it to)

There's a video for that: code-vault.net/lesson/fjri9hcdte:1642359047479