Skip to main content

JavaScript: JavaScript has Closures

Python has closures:
def outer():
print "Enter number:",
num = raw_input()
def inner():
print num
return inner

f = outer()
f()
Note that the variable num is available from within inner when outer has already completed.

Did you know that JavaScript has them too?
function testSetTimeout() {
var privateVar = 'A string';
function bar() { alert(privateVar); }
window.setTimeout(bar, 1000);
}

testSetTimeout();
The function bar makes use of privateVar which a variable in testSetTimeout's local scope even though bar is invoked later by setTimeout, i.e. after testSetTimeout has completed.

Comments

Donovan Preston said…
JavaScript even has non-neutered closures, unlike Python. In Python, there is no distinction between creating a name in an inner scope and changing the value stored in that name. JavaScript has the "var" construct (did you know that any variable declared in JavaScript without var is automatically global?) and thus has a way to distinguish between creating a new cell in an inner scope and rebinding an outer cell in a containing scope.

var accum = function() {
var i = 0;
var get = function() { return i };
var set = function() { i++ };
return [get, set];
}

var x = accum()

x[1]()
x[1]()
x[0]()


The last line will return 2.

dp
jjinux said…
Nice tip. It makes total sense. My buddy Brandon L. Golm has argued with me many times wishing that Python's global and local variables were at least declared like with "my" in Perl. I guess this is one small case where it would pay off. I've actually encountered this limitation in my code. If you really need to get around it, wrap the variable with a list, and then modify the first element of that list:

def outer():
num = [5]
def inner():
num[0] += 1
print num[0]
return inner

f = outer()
f()

(Ugh, Blogger won't let me use the pre tag to indent things.)

I saw this trick in Sam Rushing's code, so I can't take credit for it.

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

JavaScript: Porting from react-css-modules to babel-plugin-react-css-modules (with Less)

I recently found a bug in react-css-modules that prevented me from upgrading react-mobx which prevented us from upgrading to React 16. Then, I found out that react-css-modules is "no longer actively maintained". Hence, whether I wanted to or not, I was kind of forced into moving from react-css-modules to babel-plugin-react-css-modules. Doing the port is mostly straightforward. Once I switched libraries, the rest of the port was basically:
Get ESLint to pass now that react-css-modules is no longer available.Get babel-plugin-react-css-modules working with Less.Get my Karma tests to at least build.Get the Karma tests to pass.Test things thoroughly.Fight off merge conflicts from the rest of engineering every 10 minutes ;) There were a few things that resulted in difficult code changes. That's what the rest of this blog post is about. I don't think you can fix all of these things ahead of time. Just read through them and keep them in mind as you follow the approach above.…