There’s one more way to create a function. It’s rarely used, but sometimes there’s no alternative.
The syntax for creating a function:
let func = new Function ([arg1[, arg2[, ...argN]],] functionBody)
In other words, function parameters (or, more precise, names for them) go first, and the body is the last. All arguments are strings.
That’s easy to understand by example.
For instance, here’s a function with two arguments:
If there are no arguments, then there’s only one single argument, function body:
The major difference from other ways we’ve seen – the function is created literally from a string, that is passed at run time.
All previous declarations required us, programmers, to write the function code in the script.
new Function allows to turn any string into a function, for example we can receive a new function from the server and then execute it:
let str = ... receive the code from the server dynamically ... let func = new Function(str); func();
It is used in very specific cases, like when we receive the code from the server, or to dynamically compile a function from a template. The need for that usually arises at advanced stages of development.
Usually, a function remembers where it was born in the special property
[[Environment]]. It references the Lexical Environment from where it’s created.
But when a function is created using
new Function, its
[[Environment]] references not the current Lexical Environment, but instead the global one.
Compare it with the regular behavior:
This special feature of
new Function looks strange, but appears very useful in practice.
Imagine that we really have to create a function from the string. The code of that function is not known at the time of writing the script (that’s why we don’t use regular functions), but will be known in the process of execution. We may receive it from the server or from another source.
Our new function needs to interact with the main script.
Maybe we want it to be able to access outer local variables?
For instance, if a function has
let userName, minifier replaces it
let a (or another letter if this one is occupied), and does it everywhere. That’s usually a safe thing to do, because the variable is local, nothing outside the function can access it. And inside the function minifier replaces every mention of it. Minifiers are smart, they analyze the code structure, not just find-and-replace, so that’s ok.
new Function could access outer variables, then it would be unable to find
Even if we could access outer lexical environment in
new Function, we would have problems with minifiers.
The “special feature” of
new Function saves us from mistakes.
And it enforces better code. If we need to pass something to a function, created by
new Function, we should pass it explicitly as arguments.
The “sum” function actually does that right:
let func = new Function(arg1, arg2, ..., body);
For historical reasons, arguments can also be given as a comma-separated list.
These three mean the same:
new Function('a', 'b', 'return a + b'); // basic syntax new Function('a,b', 'return a + b'); // comma-separated new Function('a , b', 'return a + b'); // comma-separated with spaces
Functions created with
new Function, have
[[Environment]] referencing the global Lexical Environment, not the outer one. Hence, they can not use outer variables. But that’s actually good, because it saves us from errors. Explicit parameters passing is a much better thing architecturally and has no problems with minifiers.