No, that's not a typo. (function(){})(); has a lot of punctuation, but that's what it really looks like. It's easier to
understand if you break it down:
( // 1
function // 2
() // 3
{ // 4
alert("code goes here");
} // 5
) // 6
(); // 7
var mathStuff = (1 + 2) * 3 means to figure out 1 + 2 first.function() { ... } In this case there are no arguments, but just you wait...someFunction by typing someFunction();.Waitaminute... What's the purpose of defining a function if we run it immediately and throw it away?
Why not just type alert("code goes here") and avoid that whole squiggly mess?
Scope, that's why. Any variables or functions created in that anonymous function live and die with that anonymous function. A major concept of scope in javascript is inner functions can see into outer functions, but outer functions can't see into inner functions. For example:
function withInline(){
var year = (new Date()).getFullYear();
(function(year){
var lastYear = year - 1; // hidden from withInline!
year++; // modifies this inner function's argument only
alert("next year is " + year); // correct
})(year); // passing the outer function's variable to the anon function
alert("this year is " + year); // unchanged
alert("last year is " + lastYear); // error: lastYear is not defined in this scope!
}
function withoutInline(){
var year = (new Date()).getFullYear();
var lastYear = year - 1; // not hidden
year++;
alert("next year is " + year); // correct
alert("this year is " + year); // incorrect, overwritten :(
alert("last year is " + lastYear); // correct
}
Notice both withInline and withoutInline execute the statements in the exact same order.
However, the withInline() button will only display two alert boxes, the third one throws an error because
lastYear is not visible to withInline, it lives and dies with the anonymous inner function.
The withoutInline() button doesn't throw any errors, but the value stored in year is
overwritten with next year! The anonymous function construct creates its own scope, or execution context.
I'm a Front-End Engineer at Yahoo! working on the Mail and Messenger teams. I blog about web design and development topics including accessibility, usability, performance, and developing HTML / CSS / JavaScript applications on Appcelerator Titanium and Adobe AIR.
If you're a web developer, you might enjoy Jelo, my JavaScript library.
All original work on this site is covered by a Creative Commons Attribution 3.0 license unless otherwise specified.
You may share or use any code or images from this site in any manner, for free, so long as reasonable effort has been made to give credit where due.
The views expressed in the posts and comments on this blog do not necessarily reflect the views of Yahoo!