Thanks, I had missed that paragraph in the manual! So without the closureScope
template the loop just generates one closure with the intances used in the last
iteration and every proc that tries to make a capture actually captures that
closure, is that correct?
Also, it is totally unrelated, but is there a specific reason why I cannot
compile the generated Javascript source with the closure compiler?
It gives me an error because of an undeclared variable in a loop
nimcache/jpacrepo.js:1727: ERROR - variable property is undeclared
for (property in x_147603) {
simply replacing "property" with "var property" seems to fix the issue (the
variable 'property' seems to be used only within the scope of the for loop,
it's not used as a global variable, so this should be safe to do)
