Follows an extract from Closure: The Definitive Guide by Michael Bolin. It might look a bit lengthy, but it's saturated with a lot of insight. From "Appendix B. Frequently Misunderstood JavaScript Concepts":
What this
Refers to When a Function is Called
When calling a function of the form foo.bar.baz()
, the object foo.bar
is referred to as the receiver. When the function is called, it is the receiver that is used as the value for this
:
var obj = {};
obj.value = 10;
/** @param {...number} additionalValues */
obj.addValues = function(additionalValues) {
for (var i = 0; i < arguments.length; i++) {
this.value += arguments[i];
}
return this.value;
};
// Evaluates to 30 because obj is used as the value for 'this' when
// obj.addValues() is called, so obj.value becomes 10 + 20.
obj.addValues(20);
If there is no explicit receiver when a function is called, then the global object becomes the receiver. As explained in "goog.global" on page 47, window is the global object when JavaScript is executed in a web browser. This leads to some surprising behavior:
var f = obj.addValues;
// Evaluates to NaN because window is used as the value for 'this' when
// f() is called. Because and window.value is undefined, adding a number to
// it results in NaN.
f(20);
// This also has the unintentional side effect of adding a value to window:
alert(window.value); // Alerts NaN
Even though obj.addValues
and f
refer to the same function, they behave differently when called because the value of the receiver is different in each call. For this reason, when calling a function that refers to this
, it is important to ensure that this
will have the correct value when it is called. To be clear, if this
were not referenced in the function body, then the behavior of f(20)
and obj.addValues(20)
would be the same.
Because functions are first-class objects in JavaScript, they can have their own methods. All functions have the methods call()
and apply()
which make it possible to redefine the receiver (i.e., the object that this
refers to) when calling the function. The method signatures are as follows:
/**
* @param {*=} receiver to substitute for 'this'
* @param {...} parameters to use as arguments to the function
*/
Function.prototype.call;
/**
* @param {*=} receiver to substitute for 'this'
* @param {Array} parameters to use as arguments to the function
*/
Function.prototype.apply;
Note that the only difference between call()
and apply()
is that call()
receives the function parameters as individual arguments, whereas apply()
receives them as a single array:
// When f is called with obj as its receiver, it behaves the same as calling
// obj.addValues(). Both of the following increase obj.value by 60:
f.call(obj, 10, 20, 30);
f.apply(obj, [10, 20, 30]);
The following calls are equivalent, as f
and obj.addValues
refer to the same function:
obj.addValues.call(obj, 10, 20, 30);
obj.addValues.apply(obj, [10, 20, 30]);
However, since neither call()
nor apply()
uses the value of its own receiver to substitute for the receiver argument when it is unspecified, the following will not work:
// Both statements evaluate to NaN
obj.addValues.call(undefined, 10, 20, 30);
obj.addValues.apply(undefined, [10, 20, 30]);
The value of this
can never be null
or undefined
when a function is called. When null
or undefined
is supplied as the receiver to call()
or apply()
, the global object is used as the value for receiver instead. Therefore, the previous code has the same undesirable side effect of adding a property named value
to the global object.
It may be helpful to think of a function as having no knowledge of the variable to which it is assigned. This helps reinforce the idea that the value of this will be bound when the function is called rather than when it is defined.
End of extract.
a
in apply for array of args andc
in call for columns of args. – Larry Battlefn(...input)
where input is an array. developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/… – Gajus