Content deleted Content added
elab local, lifetime vs. context vs. scope |
Fixed a couple of misconceptions, made it slighly more general, and added some historical background. |
||
Line 1:
__NOTOC__
In [[computer programming]], an '''automatic variable''' is a local [[Variable (programming)|variable]] which is allocated and deallocated automatically when program flow enters and leaves the variable's
Automatic local variables primarily applies to recursive [[scope (programming)|lexically-scoped]] languages. Automatic local variables are normally [[Stack-based memory allocation|allocated in the stack frame]] of the procedure in which they are declared<ref>unless otherwise specified, such as static or heap-based data, which are specifiable in some languages</ref>. This was originally done to achieve [[reentrant (subroutine)|re-entrancy]] and allowing [[recursion]],<ref>When the reentrant property of the routine is used, for recursion or otherwise, the [[compiler optimization|optimizer]] must ''not'' try to allocate such variables in [[processor register]]s (for efficiency) as this would break the reentrancy.</ref> considerations that still applies, although the concept of recursive (and [[nested function|nested]]) functions in a lexically scoped language was introduced to the wider audience already with [[ALGOL]] in the late 1950s (and then further popularized by its many descendants).
The term ''[[local variable]]'' is usually synonymous with automatic variable, since these are the same thing in many programming languages, but local is more general – most local variables are automatic local variables, but [[static local variable]]s also exist, notably in C. For a static local variable, the allocation is static (the lifetime is the entire program execution), not automatic, but it is only in scope during the execution of the function.
==In specific programming languages==
|