static.h:
static.c:Code:static int t = 4;
static2.cCode:#include <stdio.h> #include <stdlib.h> #include "static.h" /*int t=7; Does not work */ int main(void) { printf("%i\n", t); return 0; }
Shouldn't there be an error when compiling like this:Code:int t=6;
Because there should be conflicts with the 2 t integers.Code:gcc static.c static2.c
The output is 4
using static on a global object (be it a variable or a function) means to only link internally.
Seems OK to me, as far as it goes.
Of course, the real problem would arise when you tried to access the t in static2.c from within static.c
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Ok, well I'll just try to be careful with what variables I choose to be static for the .c/.h duo files. I just needed to make sure it wasn't a concept I missed or something like that.
Well I wouldn't normally initialise statics inside header files for starters.
That kinda limits including that header file in ONE .c file, which is of limited use (though not entirely useless).
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Header files have:
-prototypes for functions
-All global variables (?)
-All #define macros (?)
C Files:
-Fill up the functions
-Fill up the variables
Am I going ok here? As standard philosophy for C programming, am I going in the right direction as far as programming structure?
>Am I going ok here?
Looks okay to me. Of course, how you structure your modules would be dependent on the application, but for the general case your list is fine.
My best code is written with the delete key.
