External variable

In the C programming language, an external variable is a variable defined outside any function block. On the other hand, a local (automatic) variable is a variable defined inside a function block.
Definition, declaration and the codice_1 keyword.
To understand how external variables relate to the codice_1 keyword, it is necessary to know the difference between defining and declaring a variable. When a variable is "defined", the compiler allocates memory for that variable and possibly also initializes its contents to some value. When a variable is "declared", the compiler requires that the variable be defined elsewhere. The declaration informs the compiler that a variable by that name and type exists, but the compiler does not need to allocate memory for it since it is allocated elsewhere.
The codice_1 keyword means "declare without defining". In other words, it is a way to explicitly declare a variable, or to force a declaration without a definition. It is also possible to explicitly define a variable, i.e. to force a definition. It is done by assigning an initialization value to a variable. If neither the codice_1 keyword nor an initialization value are present, the statement can be either a declaration or a definition. It is up to the compiler to analyse the modules of the program and decide.
A variable must be defined exactly once in one of the modules of the program. If there is no definition or more than one, an error is produced, possibly in the linking stage. A variable may be declared many times, as long as the declarations are consistent with each other and with the definition (something which header files facilitate greatly). It may be declared in many modules, including the module where it was defined, and even many times in the same module. But it is usually pointless to declare it more than once in a module.
An external variable may also be declared inside a function. In this case the codice_1 keyword must be used, otherwise the compiler will consider it a definition of a local (automatic) variable, which has a different scope, lifetime and initial value. This declaration will only be visible inside the function instead of throughout the function's module.
The codice_1 keyword applied to a function prototype does absolutely nothing (the codice_1 keyword applied to a function definition is, of course, non-sensical). A function prototype is always a declaration and never a definition. Also, in standard C, a function is always external, but some compiler extensions allow a function to be defined inside a function.
Scope, lifetime and the codice_8 keyword.
An external variable can be accessed by all the functions in all the modules of a program. It is a global variable. For a function to be able to use the variable, a declaration or the definition of the external variable must lie before the function definition in the source code. Or there must be a declaration of the variable, with the keyword codice_1, inside the function.
The codice_8 keyword (codice_8 and codice_1 are mutually exclusive), applied to the definition of an external variable, changes this a bit: the variable can only be accessed by the functions in the same module where it was defined. But it is possible for a function in the same module to pass a reference (pointer) of the variable to another function in another module. In this case, even though the function is in another module, it can read and modify the contents of the variable—it just cannot refer to it by name.
It is also possible to use the codice_8 keyword on the definition of a local variable. Without the codice_8 keyword, the variable is automatically allocated when the function is called and released when the function exits (thus the name "automatic variable"). Its value is not retained between function calls. With the codice_8 keyword, the variable is allocated when the program starts and released when the program ends. Its value is not lost between function calls. The variable is still local, since it can only be accessed by name inside the function that defined it. But a reference (pointer) to it can be passed to another function, allowing it to read and modify the contents of the variable (again without referring to it by name).
External variables are allocated and initialized when the program starts, and the memory is only released when the program ends. Their lifetime is the same as the program's.
If the initialization is not done explicitly, external (static or not) and local static variables are initialized to zero. Local automatic variables are uninitialized, i.e. contain "trash" values.
The codice_8 keyword applied to a function definition changes the linkage of the function so that it is only visible from the translation unit where its definition is located. This prevents the function from being called "by name" from outside its module (it remains possible to pass a function pointer out of the module and use that to invoke the function). Declaring a function using the codice_8 keyword is also a good way to keep its name short while avoiding name clashes.
Example (C programming language).
File 1:
 // Explicit definition, this actually allocates
 // as well as describing
 int Global_Variable;
 // Function prototype (declaration), assumes 
 // defined elsewhere, normally from include file. 
 void SomeFunction(void); 
 int main(void) {
 Global_Variable = 1;
 SomeFunction();
 return 0;
File 2:
 // Implicit declaration, this only describes and
 // assumes allocated elsewhere, normally from include
 extern int Global_Variable; 
 // Function header (definition)
 void SomeFunction(void) { 
 ++Global_Variable;
In this example, the variable Global_Variable is "defined" in File 1. In order to utilize the same variable in File 2, it must be "declared". Regardless of the number of files, a global variable is only "defined" once; however, it must be "declared" in any file outside of the one containing the definition.
The normal methodology is for allocation and actual definitions to go into .c files, but mere declarations and prototypes do not allocate and just describe the types and parameters so that the compiler can work correctly, and that information belongs in a .h header file that others can safely include without any possible conflict.