Comments on: c’t magazine: WebZwoNullTurbo, how to optimize JavaScript

By: Michael

Michael — Thu, 15 Apr 2010 09:51:35 +0000

5) My experience. See also http://javascript.crockford.com/memory/leak.html, even though IE6 is outdated now and there were many improvements concerning memory management.

By: Tobias

Tobias — Tue, 02 Feb 2010 05:28:57 +0000

5) Why?

By: Michael

Michael — Wed, 19 Aug 2009 11:08:10 +0000

Yes, you can do it with a closure and private variables, but this can cause memory leaks, especially when you do AJAX calls in the closure.

Local means object instance properties like this.value (so “this” is the context). Also just using the variable in the argument of the anonymous function is common mistake, which will not work.

By: Michael S.

Michael S. — Tue, 18 Aug 2009 19:13:31 +0000

Are you sure setTimeout(doSomething) doesn’t work in IE? I don’t have an IE around to test it, but I though that construction worked fine. MSDN seems to indicate it works as well:

http://msdn.microsoft.com/en-us/library/ms536753(VS.85).aspx

You could do

setTimeout(function() { doSomething(foo, bar, baz); }, …)

to close over local variables I guess.