hey guys...i don't understand why there are global and local variables. why can't we use all the variables as global? if we declared an integer as global, it takes the same memory as local does. correct me if was wrong.
hey guys...i don't understand why there are global and local variables. why can't we use all the variables as global? if we declared an integer as global, it takes the same memory as local does. correct me if was wrong.
1.) If there were no local variables, you would have to declare all your variables globally, thus a part of your code would look like a "Dictionary" rather than a C program.
2.) One part of a code could easily modify the contents of a varible any time and it would be difficult for you to trace out what modified it (the changes would ofcourse be reflected globally).
3.) Variable naming space would shrink. You would not have too many choices on naming variables.
4.) Memory is allocated to Global variables during compile time itself, shortening the space available to your program.
It's always a good practice to avoid Global variables as much as possible. But there are places where using it is really an advantage. At the end of the day, you are the coder, the choice is yours.
you would need things like say, int i, I, i_, I_, i2, I2; for all the loops you use or something. your program will become very unmodular.
You are incorrect.
Global variables are allocated at compile time. That means that however many bytes it takes to hold all your global variables, is created as a binary block and included as part of the size of the executable. Hardcoded, as it were. Globals are addressed relative to the start of your code.
Local variables however, are allocated on the fly when a function is called. You may have heard the term 'stackframe'. Whenever a function or procedure is called, a stackframe is created on the stack that contains the function/proc's variables and return value (if any). Then while the variables are in use, they are referenced relative to the start of the function/proc, on the stack. When the function terminates, the calling code grabs the return value (if any), and disposes of the used stackspace holding the stackframe.
The main reason you have two kinds of variables is for scope. It makes no sense to create a function/proc that uses variables for its own purposes and make those variables available to everyone. To do so increases the link size, RAM requirements, and slows things down.
Global variables take more processor time to access, because they use a larger pointer and the relative offset is farther. Local variables only need a small offset, so they can be accessed faster from within the function than a global variable.
If you want to know more about this, read about variable 'scope'.
Ooops, I meant that the original 'Unregistered' poster was incorrect.
If you want to become a good programmer, try not to use global variables. Read up about coupling and cohesion of modules/functions.
