Nicholas,

So closures can't be created if you only use the Function constructor to create new functions.

Is there a situation where using the contructor is better?

Thanks

Christian

That's not entirely a correct statement. The rule is:

You cannot capture variables outside of function scope when using the Function constructor. You can create closures, like this:

Technically, this function creates a function that is a closure (it captures the variable "a").

Generally, it's considered poor practice to use the Function constructor to create new functions, though technically it's not wrong.

Nicholas C. Zakas
Author, Professional JavaScript for Web Developers (ISBN 0764579088)
http://www.nczonline.net/

Nicholas,

What I meant was that if you used the function constructor *everytime* you wanted to define a function you wouldn't be able to do it.

If I take your code from the last post and change how you created the internal function to also use the function constructor, then it wouldn't be a closure anymore.

I really appreciate the time you take to answer my crazy questions.

Thanks

Christian

Nicholas,

Wouldn't the code on your last post return a reference to a function rather than executing the anonymous function and therefore returning the value of the variable a?

Christian