4
1)function () { 
    // code here...

}();

2)(function () { 
    // code here...

})();



3)(function () { 
    // code here...

}());

What are the differences (especially third variant)? Are they all the same?

DrStrangeLove
  • 11,227
  • 16
  • 59
  • 72
  • You can find more information on this at http://stackoverflow.com/questions/440739/what-do-parentheses-surrounding-a-javascript-object-function-class-declaration-me and http://stackoverflow.com/questions/423228/difference-between-function-and-function – Narendra Yadala Oct 04 '11 at 11:29

3 Answers3

2

1st one is not valid, however you can do following instead to make it work:

var myfunction = function () { 
    // code here...
}();

As other answers pointed out that there is no difference between 2nd and third, they are same.

Instead of using parenthesis, following is also valid:

!function() { /*  code here... */ }();
~function() { /*  code here... */ }();
+function() { /* code here... */ }();
-function() { /*  code here... */ }();
new function() { /*  code here... */ };
new function(arguments) { /*  code here... */ }(arg);

Note: People used to call these functions 'Self-Executing Anonymous Function' but the term is incorrect. Now they are called 'Immediately Invoked Function Expressions (IIFE)' pronounced "iffy"!

Gurpreet Singh
  • 20,907
  • 5
  • 44
  • 60
  • 1
    You should not use `new`, especially if you care about the return value. – Bergi Feb 07 '14 at 04:06
  • if you use `new function(){}` this will return a object with **constructor** property and I can run the function again this is prevent by non new example or IIFE example – Muhammed Albarmavi Oct 13 '18 at 11:16
2

2 and 3 are exactly equivalent. There is no functional difference between them.

1 is a syntax error. Because the function is not wrapped in brackets, it is treated as a function declaration. It is invalid because function declaration need to be named. The brackets make it a "function expression"; these do not need to be named.

lonesomeday
  • 233,373
  • 50
  • 316
  • 318
  • 1 is a syntax error for *two* reasons. Firstly, like you said, a function declaration needs to be named, but also because the trailing `()` is not valid syntax. It certainly won't execute the function just declared even if it were named... – davin Oct 04 '11 at 11:34
  • @davin Well, yes, But the parser doesn't even get to that point because of the previous error. – lonesomeday Oct 04 '11 at 11:43
2

First one gives a syntax error. Second and third versions define a anonymous function and immediately execute it. Second and third versions are also called Immediately Invoked Function Expressions.

You might also encounter another version which looks like this. This is equal in functionality to 2nd and 3rd version but it just negates the return value.

!function() {
   //some code
}()
Narendra Yadala
  • 9,554
  • 1
  • 28
  • 43
  • No, it does not give a syntax error because of the negation operator. This form just executes the function and negates the return value and returns it to the caller. – Narendra Yadala Oct 04 '11 at 11:32
  • You might want to have a look at this link http://benalman.com/news/2010/11/immediately-invoked-function-expression/ ..It covers most of the forms of self invoking functions and their differences. – Narendra Yadala Oct 04 '11 at 11:37