In Javascript, when is a new scope created? The 2 situations I know of are:
as a note, any new block (in if-then-else, loops, or just beginning a block for no other reason) won't create a new scope.
Is there a third situation where a new scope is created besides the two situations above? Thanks.
Yes, there is a third case where the scope chain is augmented (besides the let mozilla-extension that Shog9 mentions), when a catch block is evaluated:
The production Catch : catch (Identifier ) Block is evaluated as follows:
Let C be the parameter that has been passed to this production.
Create a new object as if by the expression new Object().
Create a property in the object Result(2). The property's name is Identifier, valueisC. value, and attributes are { DontDelete }.
Add Result(2) to the front of the scope chain.
Evaluate Block.
Remove Result(2) from the front of the scope chain.
Return Result(5).
So basically, a new object is created, with a property named like the Identifier passed to catch, this new object is added to the scope chain, so we are able to use that identifier within the catch block.
try {
throw "error";
} catch (identifier) {
// `identifier` accessible here..
}
But keep in mind that it only augments the current scope temporarily, to introduce the catch Identifier, any variable declared inside will be simply hoisted to the top of it enclosing function.
function getScope() { try { throw function () { return this; }; } catch (f) { return f(); } } Usually when a function using this was called without being a method, it would return the global object. But the implementers read "as though by the expression new Object()" literally and implemented it as an object inheriting from the previous scope. Once you got a scope object, you could walk up the prototype chain to get to the others.There's also the let statement. Keep in mind that let (...) {}, like with (...){}, does not create a new scope for variables introduced within the block. However, let definitions can create variables scoped to the block (any block) they're defined in.
Fair warning: as has been pointed out in comments, while let is part of JavaScript 1.7 (the Mozilla dialect of ECMA-262/ECMAScript), it is not part of ECMAScript, and will likely not work any time soon in browsers other than Firefox. Also note that while with can be used as a stand-in for let statements in current implementations of ECMAScript, the "strict" mode proposed for the pending ECMA-262 5th edition disallows this as well. If you're concerned about writing cross-plaform, future-proof code (and you should be...) then stick with functions for scope control!
let was part of the intended ECMAScript 4 spec that never came to be and my brain tends to lean toward the fact that it may return in a future update to the standard.let will be part of ECMAScript Harmony, the next step...this will also refer to the object you are in:
a = {
f: function(){ ... },
b: function(){this.f()}
}
a.b() //calls a.f
