Hmm, you could look at Visual Studio or CLion, those IDEs might have something like this integrated

I get to header files in the next video. This was just to showcase how to actually share functions first. I feel like this order of explaining the concepts makes it easy to understand header files that are otherwise a complex topic

@@CodeVault Ok, you do an excellent job, btw.

That line I was using to compile all the files is, in fact, compiling each file one by one but also linking them together directly into an executable. It's just that it doesn't save those obj files to disk

@@CodeVault oh, I see. I did not realize that it was still doing them one at a time under the hood. Thank you. By the way, many years ago I was experimenting with a GNU C compiler to try and understand the low-level details about the 4 stages of compilation: 1. Preprocess, using the -E flag with the 'gcc' program to get '*.i' files 2. Compilation, using the -S flag with the 'gcc' program to get '*.s' files 3. Assemble, with the 'as' program to get '*.o' files 4. Link, with the 'ld' program to get the final binary and wrote a makefile that did these steps one at a time. When you invoke the compiler from the command line or run a makefile, it seems that normally you either jump directly to step 4--or you jump directly to step 3, and then to step 4. It was interesting to explore these first 2 steps and open them in a text/hex editor to see what was produced. I was able to compile this way for simple projects that only had a main.c file and nothing else, but I never got it to work properly with multiple C files for some reason. I was also doing this to try to understand why certain sections of code such as .TEXT were placed in certain areas of memory. Anyhow, it would be cool someday to see a video series where you explore the guts of a C compiler like this. My weird makefile is here for reference: github.com/yankee14/avr-makefile/blob/master/Makefile

Thanks! I'll keep this in mind and will make a video series about this later on. Certainly those steps are very interesting and answers a lot of questions people might have about the whole compilation process. One interesting thing you could do, if you compile them step by step is you could link obj files together that were compiled from different languages (say C and Pascal). It's a very interesting concept that nowadays you don't see much of in modern programming languages.

@@CodeVault that is fascinating!

I will look into it

Yes you can have a simple "myfuncs.h" file where you include everything you need

I think you can use gsl for that: www.gnu.org/software/gsl/

You have to change the build task so it includes the right files (usually in tasks.json)

Yes, this works. But if you try to create another file (say utils.c), including main2.c inside and compiling it together with main.c you'll get an error since sumOfTwoNumbers will be defined in both main.c and utils.c

It's the same idea as functions. It makes them local to the file it's defined in

You can share as many functions as you want

Could be an interesting video although I haven't used Rust too much myself. Thanks for the recommendation!