Thread: Help understanding structuring multiple .c and .h files (intial linker process)

Originally Posted by anduril462

The fact that several companies do something a particular way doesn't mean it's a good thing.

I was just pointing out that it's a common practice. In my opinion and that of my co-workers at those companies, it's a practical solution to using common include files with the source files that define variables as well as the source files that use those variables.

#define VOL volatile

This one I don't get, unless the goal is to reduce the number of characters to type volatile, or perhaps to use uppercase VOL as a replacement for the keyword volatile. I can't imagine a situation where volatile would be optional depending on the source file. Normally volatile variables are those updated in interrupt routines or updated by a thread in a multi-threaded environment.