Global variables
Every variable in Javascript is a named attribute of an object. For example:-
var x = 1;
x is added to the global object. The global object is provided by the script context and may already have a set of attributes. For example in a browser the global object is window. An equivalent to the above line in a browser would be:-
window.x = 1;
Local variables
Now what if we change this to:-
function fn()
{
var x = 1;
}
When fn
is called a new object is created called the execution context also referred to as the scope (I use these terms interchangeably). x
is added as an attribute to this scope object. Hence each call to fn
will get its own instance of a scope object and therefore its own instance of the x attribute attached to that scope object.
Closure
Now lets take this further:-
function fnSequence()
{
var x = 1;
return function() { return x++; }
}
var fn1 = fnSequence();
var fn2 = fnSequence();
WScript.Echo(fn1())
WScript.Echo(fn2())
WScript.Echo(fn1())
WScript.Echo(fn2())
WScript.Echo(fn1())
WScript.Echo(fn1())
WScript.Echo(fn2())
WScript.Echo(fn2())
Note: Replace WScript.Echo
with whatever writes to stdout in your context.
The sequence you should get is :-
1 1 2 2 3 4 3 4
So what has happened here? We have fnSequence
which initialises a variable x
to 1 and returns an anonymous function which will return the value of x
and then increment it.
When this function is first executed a scope object is created and an attribute x
is added to that scope object with the value of 1. Also created in the same execution object is an anonymous function. Each function object will have a scope attribute which points to the execution context in which it is created. This creates what is know as a scope chain which we will come to later. A reference to this function is returned by fnSequence
and stored in fn1
.
Note that fn1
is now pointing at the anonymous function and that the anonymous function has a scope attribute pointing at a scope object that still has an x
attribute attached. This is known as closure
where the contents of an execution context is still reachable after the function it was created for has completed execution.
Now this same sequence happens when assigning to fn2
. fn2
will be pointing at a different anonymous function that was created in a different execution context that was create when fnSequence
was called this second time.
Scope Chain
What happens when the function held by fn1
is executed the first time? A new execution context is created for the execution of the anonymous function. A return value is to be found from the identifier x
. The function's scope object is inspected for an x
attribute but none is found. This is where the scope chain comes in. Having failed to find x
in the current execution context JavaScript takes the object held by the function's scope attribute and looks for x
there. It finds it since the functions scope was created inside an execution of fnSequence
, retrieves its value and increments it. Hence 1 is output and the x
in this scope is incremented to 2.
Now when fn2
is executed it is ultimately attached to a different execution context whose x
attribute is still 1. Hence executing fn2
also results in 1.
As you can see fn1
and fn2
each generate their own independent sequence of numbers.