3 ms·
I just got the first one wrong and haven't written C code in a decade. I have to admit I haven't seen that construct used in any programs. I guess, no harm no
by kenjackson 12y ago
I just got the first one wrong and haven't written C code in a decade. I have to admit I haven't seen that construct used in any programs. I guess, no harm no foul, but still seems like an odd construct to allow.
- foogoespop 12y agoThe first one would appear when using global variables which are shared across files, you just wouldn't see it as the pieces would usually be in separate files. Something like: /* file.h */ int global_i; and you have: /* file.c */ int global_i = 0; Then if file.c includes file.h both will be in the same file during compilation.