As I'm spending some time back in the land of low-level C, I'm trying to fully get my head around best-practices for header files and code organization, so I thought I'd toss out some questions ...

It isn’t very complex — the whole thing lives in one fairly large C source file but it can scan a directory and create header files for everything.

It isn’t very complex — the whole thing lives in one fairly large C source file but it can scan a directory and create header files for everything.

In C programming, a source code file that contains common definitions and data structures that all programmers may use as required. Also called "include files," because the #include statement is ...

Statements are executable and can have breakpoints set on them. Everything else can't.* Really the non-executable stuff in a header is no different than the non-executable stuff in a source file.