473,325 Members | 2,828 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,325 software developers and data experts.

closures in JavaScript

I've written a short article explaining closures in JavaScript. It's
at:

http://www.martinrinehart.com/articl...-closures.html

I think I've understood. I look forward to your constructive critique.
Oct 3 '08 #1
4 1823
Ma************@gmail.com wrote:
I've written a short article explaining closures in JavaScript. It's
at:

http://www.martinrinehart.com/articl...-closures.html

I think I've understood. I look forward to your constructive critique.
- A closure is _not_ "a bundle of data and code that manipulates that data";
that is how you could describe an *object* (and often it is done so),
which has properties and methods (which are merely callable properties in
ECMAScript implementations) to operate on these properties.

A closure is instead a subroutine (function) that reproduces its
definition context when executed. This definition context would
contain what is called "bound variables" that can then be accessed
from within the subroutine when executed (cf. Wikipedia etc.)

- Inner functions, by which you mean function declarations within function
declarations, must be distinguished from function expressions that you
are using later in your article to create closures.

While both constructs can create a closure, the former cannot create
closures with bound "variables" that are created after variable
instantiation. In contrast to function expressions, function declarations
cannot be within a block statement, so they cannot be conditional (except
with evil[tm] eval()).

I find calling a function expression an "inner function" to be confusing
at best. That is a term that I would use only for nested function
declarations.

And while the Specification makes no statement regarding the nesting depth
of functions (be they declared or created through an expression), there is
most certainly a practical limit, stack size included. IIRC we have
discussed this here before.

- I disagree with your sentiment that JS/ES was more pythonic than Python;
knowing both languages quite well, when it comes to power of expression
ECMAScript implementations still have a lot to learn from Python.
Incidentally, they are beginning to: read Brendan Eich's blog regarding
this; then consider Array comprehensions being supported since JavaScript
1.7 (Gecko 1.8.1/Firefox 2.0.x), which is but a Python copycat.

- The statement "In addition to explicitly declared parameters and vars,
there are other things. You can access some of them directly, such as
this and arguments." is wrong, because neither of the mentioned features
are either parameters or variables.

`this' is a keyword and a (Reference) value that refers to the calling or
constructed object. `arguments' is a property (of the Activation/Variable
object).

- The statement "Other parts, such as the activation object and the
execution context are also present, but you cannot access them from
JavaScript." is wrong in its absoluteness, because you can access the
Activation Object of the global execution context with `this' because
the Global object is also the Variable Object of this context.

The execution context as such is not anything that is supposed to be
accessible in code because it is merely a theoretical construct.

- "When outer() returns a function it also returns a copy of its execution
context." No, it does not, that's nonsense; because again, the execution
context is only a theoretical construct.

Instead, when the Function object is created in outer() it would need to
retain some information about which of the "variables" (properties) in it
are bound to the execution context of outer() and which are not; probably
a copy of or a reference to the Variable Object of the execution context
created with the previous outer() call.

What is returned is a reference to the Function object. Whether or not
that Function object retains a copy of or a reference to the Variable
Object of the execution context created with the previous outer() call
instead, remains to be seen; I would presume this to be
implementation-dependent, although it would be more efficient to use
a reference.

- As for your example, where is `init()'?

- As for your summary, where is `grow'?
HTH

PointedEars
--
Anyone who slaps a 'this page is best viewed with Browser X' label on
a Web page appears to be yearning for the bad old days, before the Web,
when you had very little chance of reading a document written on another
computer, another word processor, or another network. -- Tim Berners-Lee
Oct 3 '08 #2
Thomas 'PointedEars' Lahn wrote:
- The statement "In addition to explicitly declared parameters and vars,
there are other things. You can access some of them directly, such as
this and arguments." is wrong, because neither of the mentioned features
are either parameters or variables.

`this' is a keyword and a (Reference) value that refers to the calling or
constructed object. `arguments' is a property (of the Activation/Variable
object).
Ignore that; I misunderstood your statement.

However, I think it is wrong to say that that (function) parameters are
declared: function *expressions* are _not_ *declarations* and still have a
parameter list (better: arguments). I am not sure what to use instead;
"Definition"/"defined" sounds better to me here.
PointedEars
--
realism: HTML 4.01 Strict
evangelism: XHTML 1.0 Strict
madness: XHTML 1.1 as application/xhtml+xml
-- Bjoern Hoehrmann
Oct 3 '08 #3
On Oct 3, 4:29*pm, MartinRineh...@gmail.com wrote:
I've written a short article explaining closures in JavaScript. It's
at:

http://www.martinrinehart.com/articl...-closures.html

I think I've understood. I look forward to your constructive critique.
Martin,

I don't agree with this:

"Some things are worth repeating: When outer() returns a function it
also returns a copy of its execution context. That is not a reference
to its execution context, it is a copy. (Probably it's a reference to
a copy, but that's an implementation detail we don't need to worry
about.) That is why I added "Sort of." when I said the closure had
access to the vars (and so on) of the outer function. It really has
access to a new set of vars (and so on) that are an exact copy of the
outer function's execution context at the time the closure was
returned by outer()."

I think that the execution context of the outer function is not copied
nowhere, it's just that it's not destroyed, it's kept in memory for as
long as the references to inner functions exist. It will last as long
as those references. Consider this example:

<html><head>
<script>
window.onload= function () {
var e, capturedInAClosure= 0;
document.body.appendChild(e=
document.createElement('button')).innerHTML= "doIt";
e.onclick= function () { e.innerHTML= ++capturedInAClosure };
document.body.appendChild(e=
document.createElement('button')).innerHTML= "doItAgain";
e.onclick= function () { e.innerHTML= ++capturedInAClosure };
document.body.appendChild(e= document.createElement('p')).innerHTML=
capturedInAClosure;
};
</script>
</head><body></body></html>

2 references to 2 inner functions remain after returning from
window.onload: doIt.onclick() and doItAgain.onclick(). Both point to
the very same 'capturedInAClosure' var, end the very same 'e'. So they
are sharing the execution context of window.onload. It's not 'a copy'
nor a 'new set of vars that are an exact copy' of the outer function.

Don't you think so ?

--
Jorge.
Oct 3 '08 #4
On Oct 3, 8:37*pm, Jorge <jo...@jorgechamorro.comwrote:
>
2 references to 2 inner functions remain after returning from
window.onload: doIt.onclick() and doItAgain.onclick(). Both point to
the very same 'capturedInAClosure' var, end the very same 'e'. So they
are sharing the execution context of window.onload. It's not 'a copy'
nor a 'new set of vars that are an exact copy' of the outer function.
Also, everytime the outer function is called, a new execution context
is created:

<html><head>
<script>
window.onload= function () {
var e, capturedInAClosure= 0;
document.body.appendChild(e=
document.createElement('button')).innerHTML= "doIt";
e.onclick= function () { e.innerHTML= ++capturedInAClosure };
document.body.appendChild(e=
document.createElement('button')).innerHTML= "doItAgain";
e.onclick= function () { e.innerHTML= ++capturedInAClosure };
document.body.appendChild(e= document.createElement('p')).innerHTML=
capturedInAClosure;
if (!arguments.callee.inited) {
arguments.callee.inited= true;
setTimeout(window.onload,0);
setTimeout(window.onload,0);
setTimeout(window.onload,0);
}
};
</script>
</head><body></body></html>

--
Jorge.
Oct 3 '08 #5

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

14
by: Alexander May | last post by:
When I define a function in the body of a loop, why doesn't the function "close" on the loop vairable? See example below. Thanks, Alex C:\Documents and Settings\Alexander May>python Python...
5
by: paolo veronelli | last post by:
I've a vague idea of the differences,I don't know scheme anyway. I'd like to see an example to show what is missing in python about closures and possibly understand if ruby is better in this...
4
by: Marc Tanner | last post by:
Hello, I am currently working on a eventhandling system or something similar, and have the problem of loosing scope. I have read many interesting posts on this group and the faq article about...
2
by: Jake Barnes | last post by:
Using javascript closures to create singletons to ensure the survival of a reference to an HTML block when removeChild() may remove the last reference to the block and thus destory the block is...
10
by: Emre Sevinc | last post by:
Take a look at the following snippet: <html> <head> <script> function add(elementId) { var container = document.getElementById(elementId); for (var i = 0; i < 10; i++) { var elt =...
5
by: Leo Meyer | last post by:
Hello, somewhere I have read that JavaScript supports closures. Does someone know how to make them work? What I want to do is this: function f1(x, obj) { var eventhandler =...
16
by: Karl Kofnarson | last post by:
Hi, while writing my last program I came upon the problem of accessing a common local variable by a bunch of functions. I wanted to have a function which would, depending on some argument,...
40
by: MartinRinehart | last post by:
I've rewritten a short article explaining closures in JavaScript. It's at: http://www.martinrinehart.com/articles/javascript-closures.html A big Thank You to PointedEars and Jorge for helping...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.