Are there any drawbacks to declaring variables in header files without the “extern” keyword?

The drawback of your code is that you will probably get a linker error. 1.

Up vote 0 down vote favorite share g+ share fb share tw.

I've recently begun to realize that the use of the "extern" keyword is highly encouraged. Thus I began to wonder if there is anything wrong with the current (extern-less) way I use header files: main. C: #include main.

H #include function. H int main(void){ globalvariable = 0; testfunction(); return; } main. H: #ifndef MAIN_H_ #define MAIN_H_ int globalvariable; #endif /* MAIN_H_ */ function.

C: #include main. H #include function. H testfunction(){ globalvariable++; return; } function.

H: #ifndef MAIN_H_ #define MAIN_H_ void testfunction(void); #endif /* MAIN_H_ */ Thus every new source file that needs access to globalvariable simply needs to include main.h. One obvious drawback to this method is arrays: you can't use {element0, element1, ...} formatting to assign values to an array once it has been declared. By the way, when I give globalvariable an initial value of zero, am I defining it at that point?

Or is memory allocated earlier? Also, is there an official term for the method I'm using? C header-files extern link|improve this question asked 4 hours agoSharpHawk113.

The extern keyword is not highly encouraged; you should use it only when you absolutely must (which hopefully is never). – Oli Charlesworth 4 hours ago stackoverflow.com/questions/1433204/… – cnicutar 4 hours ago Global variables are bad. – Fred Larson 4 hours ago Interesting.

The feeling I'd gotten from previous threads here was that extern was the de facto way of doing things. – SharpHawk 4 hours ago 1 @SharpHawk: No (there isn't). I'm implying that you should be avoiding global variables shared between multiple translation units... – Oli Charlesworth 3 hours ago.

The drawback of your code is that you will probably get a linker error.1 1. Where "probably" is based on the notion of building your code on a whole bunch of different toolchains.

– Oli Charlesworth 4 hours ago No, I've only used it in AVR Studio 5 (an admittedly terrible program). – SharpHawk 4 hours ago.

The problem with this is that you may get linking errors due to multiple definitions when you try to link your program. You're depending on implementation defined behavior here -- the implementation is allowed to treat the duplicate definitions as all referring to a single object, but is not required to.

Extern int globalvariable; is a declaration int globalvariable; is both a declaration and a tentative definition. In C, it's illegal for the same variable to have multiple definitions, and that will happen if you use the latter in a header file that's included in more than one translation unit. Unix systems however historically allow this usage, so most compilers will accept the code despite it being invalid C.

If so, that's exactly what I'm doing, and as you stated in your last line, the compiler doesn't complain. In fact, it doesn't even produce a warning. – SharpHawk 4 hours ago Right.

The compiler can't complain because each individual translation unit is valid; only the linker could complain, and it doesn't, because it's traditional on unix to allow this. That still doesn't make it valid C, and it's not doing what you want. (It's collapsing multiple definitions of the variable into one at link-time rather than declaring that you want to access a variable defined in another translation unit.

) – R.. 4 hours ago.

The only official term that I know of for the method you are using is "implementation dependent behavior". You will run into all sorts of problems with that method once you start building with different compilers (or possibly even different versions of the same compiler). Some will throw a linker error, but some will accept it (although there's no guarantee exactly how it will be interpreted).

I highly recommend that you adopt a more standard approach that compilers will interpret in a predictable way. The definition for a variable needs to be in a . C file.

If you want to access that variable from another . C file, add an extern declaration in a header. This technique is standard C and will be interpreted predictably on any conforming compiler.

To answer your allocation question, memory for all globals is allocated before the program starts running. A global variable takes up space even if it is only used in a subsection of the code that never runs. Your globalvariable = 0; line isn't actually giving the variable an initial value.

The C compiler will make sure that all uninitialized global variables are automatically initialized to zero when the program loads. Your code is technically re-assigning the variable's value. If you want to make sure that a global is initialized to a particular value, add the initializer to the definition like int globalvariable = 42;.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.